NOTICE:
This content is in the "archives" of a retired blog called Gadgetopia. It has been moved to this subdomain as it is no longer considered relevant to the site. It is being hosted here for a indeterminate period of time. Its existence at this URL is not guaranteed, and it may be removed at any time. If you would like to refer to this content in the future, you are encouraged to save it to your local file system.

Some content from Gadgetopia was moved to the technical blog on deanebarker.net

Posts vs. Pages

Originally published by "dbarker" on 2003-08-01 13:40:00Z

CMS Needs:

“Why is it that nearly every open source CMS thinks they should look and act like a clone of Slashdot?”

Agreed. phpNuke, postNuke, phpWebSite – they all look the same. Most CMSs these days are concentrated on the blog-fueled phenomenon of the “post” being the most granular content unit. What about smaller sites that are not a collection of posts, but a collection of pages?

Comment by "mike" on 2003-08-18 14:20:00Z

i totally agree with you...pages is what i need.

Comment by "Deane" on 2003-08-18 14:53:00Z

CityDesk is good for this. It will do both automated indices, blog style, or you can use it just like a WYSIWYG client with templating. A good compromise for most people.

Comment by "Viesis" on 2005-08-15 17:31:00Z

Webinsta could do the thing

Comment by "sweeta-eo" on 2008-03-27 08:22:00Z

Sorry, but what is kimerikas? Jane.