Actually... restricting to two levels would need extra effort. The category / subcategory relation is based on the document / parent relation, so from the development point of view there's no difficulty here. Also, the already implemented methods for displaying the categories support deep hierarchies.
In order to participate to the quality improvment effort, here are some remarks written after testing the blog app for a client project. Pick in it what you consider relevant :-)
Thanks for the feedback. Most of the problems come from the categories UI, which was left half-baked for the initial blog release. The new categories UI will solve most of these issues.
About sub-sub-sub category : IMO, only two level is enough. I notice it because perhaps we may spend our effort on other improvment aspects
Actually... restricting to two levels would need extra effort. The category / subcategory relation is based on the document / parent relation, so from the development point of view there's no difficulty here. Also, the already implemented methods for displaying the categories support deep hierarchies.
In order to participate to the quality improvment effort, here are some remarks written after testing the blog app for a client project. Pick in it what you consider relevant :-)
Thanks for the feedback. Most of the problems come from the categories UI, which was left half-baked for the initial blog release. The new categories UI will solve most of these issues.
(see the attachment tab, sorry)