Long a selling point for Drupal, robust categorization and tagging of content is receiving a long overdue overhaul in Drupal 7. Meanwhile, contributed modules continue to be added and improved that leverage taxonomy for displaying, searching, filtering, sorting, and recommending content– and for connecting your site to other sites and classification methods.
Ironically, the plethora of contributed taxonomy modules are as poorly organized and hard to keep track of as any set of Drupal projects. We'll help you make sense of it all.
We all love CCK and Views! With lots of amazing field modules out there, you can create almost any content type you need without writing a single line of code, have a reasonably usable form into which to add your content, and create pages that let you slice and dice that content in all sorts of ways. As a result, a big part of site architecture now is planning what content types you need and what fields are needed to represent that content type. Fields have become such an important way of structuring a Drupal website that starting with Drupal 7, the entire Field API is part of core. We've almost removed the need for writing code to build a custom content type. Almost, but not quite! What happens if you need to group fields and then build content that needs multiple instances of the group?
Three years ago, Dries Buytaert announced that Content Mangement Systems had eliminated the webmaster, and challenged the Drupal community to eliminate the developer, too.
