I'm now currenly doing my internship for my degree program in an computer system support company. My supervisor gave me a task to re-build their current homepage and an intranet for the company and I am planning to use drupal for the new homepage. However, I got myself confused after trying to build books and taxonomy (I am new to drupal). Can anyone give me some suggestion on how to use combination of books and taxonomy to manage the site content?
The homepage part is meant for visitors to know about the company, with content like follows:
Homepage (Should this be a book?)
|- About Us (a page)
|- Our Products (Another Book?)
|- |- Product A (a page)
|- |- Product B (a page)
|- Our Solutions (Yet Another Book?)
|- |- Solution A (a page)
|- |- Solution B (a page)
|- News & Announcements (Book?)
|- |- News Item A (a story)
|- |- News Item B (a story)
|- |- News Item C (a story)
for the structure above, do I use taxonomy and terms or books to categorize the content?
The knowledgebase on the other hand is meant only for the customers and internal staff. I guess I can use Taxonomy Access Control module to define the access level. And the hierachy will be just as follows
Knowledge Base (Do I need to create a book for this?)
|- Server Related (A book?)
|- |- .... (Another book?)
|- |- |- ... (a page/story?)
|- |- |- ... (a page/story?)
|- Desktop PC Related (Book?)
|- |- ... (Another book?)
|- |- |- ... (a page/story?)
|- |- |- ... (a page/story?)
|- Software Related (Book?)
|- |- Firefox (Book?)
|- |- |- Installation Guide (page/story?)
|- |- |- Backup Guide (page/story?)
|- |- |- Bookmarking (page/story?)
|- |- Thunderbird (Book?)
|- |- |- Installation Guide (page/story?)
|- |- |- Backup Guide (page/story?)
|- Hardware Related (Book?)
|- |- Optical Drives (Book?)
|- |- |- Troubleshooting Guide (page/story?)
|- |- |- Some other guide (page/story?)
does the configuration makes sense? how can i do taxonomy? any comment/suggestion?
thanks in advance for your help
p/s: sorry, my english seems very poor :P
Comments
would using forum module
would using forum module makes the knowledgebase part of the system easier to setup?
looks fine to me
your approach looks good to me. I actually implemented similar approach. I had to make the choice between using books vs. taxonomy and ended up using later for these reasons...
- I can use TAC to control role-based access more granularly (can be done with books but not at this level).
- I use taxonomy context to show the menu, breadcrumbs, and term description.
- I use the mighty 'views' modules to render node term node listing.
- Abundance of taxonomy-based modules that allows you to scale for future needs e.g. views and rss.
I still use books to capture the boring stuff like policies and procedures. For technical content, I stuck with Taxonomies.
Hope this helps.