Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.
By robmypro on
I've been making steady progress setting up Drupal, but I sort of hit a wall on taxonomy/categorization. Our site is a corporate site, with a collection of mainly static pages. I do plan on adding a news article section, faq, downloads, and a blog, but there really aren't a lot of user comments or posts involved. News could be a story, I downloaded the faq module, and the blog is a module. So when I look at using categories and terms, I'm at a loss to understand how they would relate to our "corporate" needs. Maybe they don't and that is the simple answer, but just in case I am missing something I thought I would ask. I read the cookbook and other articles related to taxonomy on the site, but didn't see a lot that applies to our needs. We will have mainly anonymous users looking for more info about our company. Except for one or two internal users that add/edit content, it really won't be a community type site.
Maybe some of you gurus can shed a little light on this taxonomy area. I'd appreciate the help.
Thanks!
Comments
some thoughts
maybe stepping back a bit would help. if you are a visitor looking at your site, you can say "wow, neat stuff! how do i find everything related to ...?", and go from there.
sounds like you have an opportunity to use taxonomy as it was meant to be used, as a classification system. at the simplest level, it is a filing system, at the most complex...wow.
hardly a guru; still a visitor in many ways. :)
Thanks for the reply Todd.
Thanks for the reply Todd. I get what you are saying but I still have a hard time seeing how to use taxonomy. Assume for example we offer several different services.
Service A
Service B
Service C
We will have information about each of these services. They could be a story or a static page. In any case we will have dedicated menus for each. Not sure how taxonomy could be helpful. I would just create static pages for each. And for the most part each page would be created once, without additional posts related to it. So only 1 content page would be created for it. Seems again like a poor use of taxonomy.
Taxonomy looks like a good way to organize related content, but I think there is an underlying assumption that multiple postings/content will be created for each term. In our case a lot of it will be one page = one term.
I am probably not making a lot of sense, and I assume it is because the light hasn't come on yet.
I guess I am looking for the case for using taxonomy for an essentially static site. Maybe there still is, but I can't grasp it yet.
maybe don't force it?
you are making perfect sense, actually. if your site is small and everything is fairly self-evident, then maybe you don't need this additional level of organization/complexity. in a way, that is good; KISS principle.
however, keep growth in mind. if the site is planning to grow, you would like to put in the foundation stuff early, just to make maintenance a little easier down the road. but it is not a show-stopper.
nice thing about Drupal, and F/LOSS in general, you are really not forced to go down a path (other than the "don't hack core" thing, which i can deal with). don't need it? don't use it. whatever works best for you.
good luck!
That makes sense. Thanks
That makes sense. Thanks for the help Todd!