There are many valuable comments in there, but the review completely butchers vocabularies and terms. It suggests calling both "categories," which would add a whole new level of ambiguity. It makes me want to rename "Categories" to something like "Classification" just to avoid the whole issue of expecting an interface to add categories. Maybe it would be valuable for Drupal to configure a vocabulary called "Tags" out of the box with free tagging that's enabled for all content types. But it should be clear that tagging is a *subset* of what the taxonomy system can do. Including some basic sample content is a nice idea. It could be an option during the installation process. I certainly don't want sample content to be mandatory for new installations. But to be honest, a lot of the suggested changes would be harmful for how I (and my company) use Drupal, which is as a development platform more than a quick-and-easy CMS. I think we'd have to find some way to satisfy the review's concerns without confining more sophisticated use. 'Cause if someone just wants a blog, we tell them to use WordPress. No one benefits from making Drupal into "Super WordPress."