Site Structure the Agaric Way

Dan's concept: every node has a place in the site structure
Ben's addendum: All node types should NOT be presented with the full range breadcrumbs and menu highlighting for internal pages work.

The idea is that some node types will automatically categorize themselves, some will present a restricted list, and only the relatively rarely used "Page" (for static pages) will be handled by

Override the display of taxonomy terms with a panel, and you have all the benefits of a taxonomy-based site structure (breadcrumbs, menu creation, views integration, and the automatic categorization itself) with all of the customizable beauty of a straight panels, pages and menu links implementation.

Agaric's site structure vocabulary is a required vocabulary for its node types, single hierarchy (we intend it to go two deep, that is, standard primary and derived secondary links).

Cleverly, we name it:

Site Structure
Home
(none of these will be taxonomy terms)
- Featured Modules
- Featured Sites
- Latest News
Services
- Web sites (term -> panel with portfolio thumbnails in a sidebar)
- Graphic design (ditto)
- Custom Drupal development
- Consulting
Portfolio
- Sites
- ...
Projects
- Modules (term -> panel, with views of modules, module-related notes)
- Themes
- Installation Profiles
- Sites
Tech

OK, there's a problem in projects-- the hierarchy should go "Projects » Modules » Community Managed Taxonomy" for instance-- which puts us at three levels and into detail I really wanted in another vocabulary (because notes should be able to be tagged with module terms, but that doesn't mean that's their place in the site structure).

I think we're good. The Site Structure vocabulary ends there, with "Modules."

The question is how to automatically make the list of Projects (each of which should be a panel which displays that project node-- or nodes, it probably makes sense to make a new "Project" for, say, CMT when it releases version two, and both will be tagged in the Project vocabulary as "Modules » Community Managed Taxonomy").

And the answer is simply a view that lists taxonomy terms, if this is possible, and each term links to the taxonomy term replacing panel for each project. This should continue to show in a sidebar block wherever you go in (taxonomy Site Structure) Projects » Modules.

(How could an installation profile or module automatically set this up?)

The recipe:

Taxonomy_menu
Taxonomy_Defaults
Content_Taxonomy (yay Matthias!)

Replace Taxonomy page with Panel
http://drupal.org/project/panels_taxonomy

Significantly, we do not select every node type to fall under the vocabulary Site Structure. That's because Content Taxonomy and Taxonomy Defaults make an end run around taxonomy module's restrictions: much of their point is cleaning up the

To be Taxonomy Defaulted:

Audio (in Projects)
Case (in Projects)
Client (in Internal?)
Documentation
Domain (Internal? Projects?)
Image (Gallery? Internal?)
Internal
Note (in Tech?)
Portfolio
Registrar (in Internal > Registrar?)

Has its own system?

Blog entry
Event
FAQ

To be
Project (in Projects)
Testimonial
Wiki (in Projects? Tech?)

On its own:

Page