Here's a draft plan for how to organize & track content on the new site.

Some background material:
General info on taxonomy module
Web site organizing principles

Type of content: User Support Q & A

Proposed drupal module to handle this content: Forum

Classification: Forum.module automatically generates its own taxonomy. Each forum container is a term in a "Forums" vocabulary. This vocabulary can be used for other content types, however, and other vocabularies can be used for forum nodes. We need to decide what categories (if any, aside from forum containers) we want to use to organize forum postings. One idea:
use "Features" vocabulary with terms such as "email, reporting, printing, finding, installation, log codes, pledge mgmt., membership mgmt.," etc.

What happens if I try to post to a forum container?
error message: "The item Support is only a container for forums. Please select one of the forums below it."

What happens if I post to a forum which is later deleted?
"Deleting a forum or container will delete all sub-forums and associated posts as well. This action cannot be undone."

Additional questions to answer:

• How can we make the forum easily searchable?
• Can we require that forum posters mention a project, such as "ebase 2.20?"

Note from Bob: When you upgrade the Forums module, you need to run the php script referred to here:
http://drupal.org/node/90214
It's important to note that forums uses both a taxonomy vocabulary and container structure that need to be refreshed if the forum module is replaced.

Forum content maintenance tasks:

• Review topics posted to the "don't know" forum and move them to an appropriate forum, leaving a "shadow link" to the new location
• Rephrase topic titles for consistency and clarity as needed

Type of content: Articles: news, brochure pages (intended for web only, not manual)

Proposed drupal module to handle this content: Story

How STORY module uses taxonomy: Each Story node can be classified with term(s) from any number of vocabularies.

Classification: use 1 vocabulary "Topic" with terms such as "community, examples, news," etc.

Additional questions to answer:

Type of content: Products

Proposed drupal module to handle this content: static download page for current distributions we want to offer: http://test.ebase.org/download
Use Project.module for additional offerings, such as older versions, extensions/modules, contributed code?

Classification: use project module's built in classification system?

Additional questions to answer:

• How will content organized in project module interact with other content types?
• How can we make it as easy as possible to find and download a desired product? 

Type of content: Documentation (content intended for manual)

Proposed drupal module to handle this content:
Currently, doc is separate PDF's categorixed with term 74. A view of all nodes in this term is linked from a support page: http://test.ebase.org/support
For future: use Book page?

Classification: 

• Organize pages hierarchically so that they are grouped into chapters and sections according to content
• Use 1 vocabulary "Audience" with terms such as "Beginner, user, administrator, implementor, developer."

Additional questions to answer:

• How does the Docbooks feature work, and how should its behavior influence our use of drupal to organize/store/display documentation?
• How would the approach described above interact with the Projects module? Can we identify a manual as a project, and put the content in a book?

Type of content: Events

Proposed drupal module to handle this content: Events

Classification: 1 vocabulary for types of events, with terms like "committee meeting, training, product release, deadline for community input," etc.

Additional questions to answer: Can we store meeting minutes using the events module, and how can we make them easy to retrieve later? 

Type of content: Bugs

Proposed drupal module to handle this content: None - continue to use Bugzilla instead until we agree on a drupal module that serves as well as bugzilla
http://wush.net/bugzilla/ebadmin

Type of content: Feature Requests

Proposed drupal module to handle this content: None currently

Classification: Bugzilla "enhancement" category

Additional questions to answer: If there's an easy way in drupal to let end-users make feature requests, it'd be nice to have that capacity. Currently, taking them via e-mail and putting htem in BZ seems ot be adequate.

We want to use taxonomy to:

• generate a site map people can use to search for content
• support views-based navigation (such as the News view currently on the members home page)
• support "breadcrumb" at the top of each node that tells you where in the taxonomy it is and allows user to move to lists of related nodes by clicking on the "breadcrumb" path
• Organize forum postings into useful groups according to... topic? feature? process or task? Somehow.

Some admin notes:
content types can be managed here:
admin/settings/content-types

Modules installed as of 3/07 that may need additional explanation/consideration before taxonomy is decided:
aggregator
archive
basicevent
blog
blogAPI
checkout
civicrm
contact
contemplate
doclist
event_views
event_repeat
exerpt
filebrowser
front_page
image
image_gallery
location
location_views
login_destination
minutes
page_title
poll
porterstemmer
premium
profile
project_issue
site_map
sitemenu
subscriptions
taxonomy_access
taxonomy_theme
upload
user_badges
video
video_customfields
video_image
video_multidownload
video_optmetadata
video_params
video_upload
views
views_bonus
views_rss
views_theme_wizard
views_ui
votingapi
webform

Questions to resolve for each of the above modules:
- are we going to use?
- does the module interact with taxonomy in any way? If so, how?
- what are the implications for site taxonomy of desired use of the module?

Statistics module counts views of each page, and this count is visible to admins & editors.
Config here http://test.ebase.org/admin/settings/statistics
and here http://test.ebase.org/admin/access