Journal Knowledge Base

Issue Summary

Running and using Journal to build and document rather large Drupal sites unveiled some caveats:

- There are *many* journal entries, which are hard to track.
- Depending on a project's time-frame and/or deadline, journal entries are rather meaningless (like "Installed Foo module" on admin/build/modules) and do not contain important information why something has been changed.
- Most of the time, Journal is useless, because someone changed something in a module or theme (thus, independent to forms) that is not tracked at all. Causes headaches like why something suddenly works different for certain things and so on...
- possibly more...

So let's think about turning Journal into an actual knowledge base. I don't think of nodes here, because I still don't want to interfere with a site's setup too much - Journal is for site developers and administrators only.

Initial ideas:

- Add tags to journal entries, so journal entries can be searched by keywords and full-text. Adding module "Foo" is possibly related to the terms "foo, bar, baz, buzz-word-here, requirementA".
- Allow arbitrary journal entries, unrelated to forms, so themers can add information about changes to themes.
- Hardcore: Allow to select arbitrary site elements on a page (highlight like Firebug), push a button that invokes a journal entry form, which stores the current path, the HTML selector, and the journal entry in the database using AHAH/AJAX. When re-visiting this page (path), display a button to display all journal entries for this page. (Me thinks of a tight integration with admin_menu here)