Blog-Post vs CMS-Page – Why Not More Separation?
As I have learned more and more about WordPress, it seems to me that since WordPress was originally designed as a blog tool and not a CMS tool, the mentality that every piece of content on a WordPress site needs to be thought of as a ‘Post’ prevails.
Why is there little effort to make the use of WordPress as a CMS significantly more intuitive and functional by Letting ‘Posts’ be ‘Posts’ and ‘Pages’ be ‘Pages’?
Currently, ‘Pages’ are just another kind of ‘Post’, even in the database schema. ‘Pages’ should have their own table in the schema in order to separate that data entirely from ‘Posts’ to avoid data corruption and to allow for database calls relating solely to ‘Pages’.
When I want a ‘Page’ title to come up on a given ‘Page’ I have to call for ‘post-title’. Really?
When attempting to use ‘Permalinks’ to enforce user and SEO friendly URLs, there is %postname% to use for pretty links to individual ‘Posts’ but there is no %pagename% to call on? Seriously?
‘Pages’ are not ‘Posts’. ‘Pages’ CONTAIN ‘Posts’. This blurring and bleeding of the conceptual nomenclature, trying to use the ‘Post’ architecture to handle ‘Pages’ is both counter intuitive to administrators/users/designers, but also seems to have been causing all sorts of mischief on the functionality side with quirky behavior on sites where WordPress is being used as a CMS.
I am curious to know why there is not a clear differentiation and hierarchy established between ‘Pages’ and ‘Posts’.
This, in my opinion, is WordPress’ greatest failing.
I am curious to know if this is recognized as an issue by other members of the community and if it is something that is slated for refinement in later releases.
- The topic ‘Blog-Post vs CMS-Page – Why Not More Separation?’ is closed to new replies.