Drupal Site Structures
Damien McKenna
Site Architecture
- Taken for granted
- Not just the site's main menu
- Content classification
- Controlling content classification
Drupal's Taxonomy System
- Vocabulary = bucket
- Term = category
- Only one API
- No practical limits
Vocabularies System
- Arbitrary content types
- Pre-defined vs "tags"
- Multi-select
- Required
- Description
Terms System
- Hierarchal
- Multiple parents
- Synonyms
- Related terms
Taxonomy Uses
- Main site categories
- Keywords
- Tags
More Taxonomy Uses
- Forums
- Geo-location - regions, states, etc
- Product categories
- Product attributes
- Brand names
Presentation #1: Drupal Default
- taxonomy/term/123
- Simple content list
- Pagination
- PathAuto for nicer URLs
Presentation #2: Views
- admin/build/views
- taxonomy_term
- Internally replaces taxonomy/term/123
- Still use PathAuto
- Customizable, it's just a View
- Can only have one output
Presentation #3: Taxonomy_Redirect
- Customizable internal path
- taxonomy/term/123
- vs category/123
- vs usa/east-coast/florida
- Create multiple views to control output
Presentation #4: Panels
- Control page output as a panel
- Override per vocabulary
- Override per term
- You're welcome :)
Presentation #4: More Panels
- Add pieces to the page
- Nodes list
- Child terms list
- Sibling terms list
- Views - pass in arguments
Presentation #4: Panels + Views
- Build a View
- Argument - term ID
- Or term name
More metadata?
- Description
- Module to add images
- Module to add coordinates
- Modules to add more metadata
- Smart Nodequeues..
- Uh, but that's a node?
Presentation #5: Taxonomy_Node
- Attach a node to each term
- Different vocab, different content type
- Easier editorial control
Tips & Tricks
- Don't trust keyword generators
- Be careful with large vocabs
- Be careful with "Term with depth" View argument
- Don't kill your server!
