I've been using WordPress as a CMS for about 7 months now with the following core features:
- Navigation Tree: Wp_list_pages for easy navigation of pages
- Solr search engine: indexing posts only (because some pages are duplicated in the tree)
- Pages that embed posts. Just about every page contains an embedded post. The reason is so that I can reference a post in multiple places on the Tree Navigation without having to edit each page individually.
Thus, my process for managing my CMS is to:
- Create a post of new content
- Select taxonomies (for use with Solr search filtering)
- Publish post. Upon publishing, a page is automatically created with the embedded post with a parent of "Standby". This saves me some time.
- Go to Standby to see my pending pages and organize in my tree hierarchy (via CMS Tree Page View). I will duplicate the page if I wish to have the embedded post featured in multiple places in the tree.
Does my process meet my CMS needs? Yes. Does it effectively double my MySQL data? Yes. Is a page with an embedded post the best solution to creating an effective hierarchical CMS? I'm not sure.
It would be nice to organize posts in a tree hierarchy for the convenience of site navigation on the front end, without having to create a page. It is also essential that when I edit the embedded post, all pages holding that post are updated.
Is there a better way of creating a hierarchical tree and what is the reason behind posts not being hierarchical?