Ideas/features for a CMS

Wanted: Far out ideas to implement into a OS-CMS

[thing3b]

I am designing an Open Source (OS) CMS and trying to break many;
- typical programming methods of CMS's
- typical features

I am trying to make a unique CMS with unique features. The CMS already is designed for;
- Static html export.
- Managing and exporting php scripts (so that exported semi static sites can still have feed back forms, custom log monitoring etc)
- Runs on an offline server and syncronises only the updated files over FTP (for those of us on limited time dial-up)

Does anyone have any unique/interesting ideas that could be implemented into such an OS CMS, including SEO ideas?

[RyanM]

I dont know about far out ideas, if I was you I would focus on a multilingual, true multi user (with record locking), caching CMS, with comprehensive work flow management, multiple staging areas, templating support, etc. But build it well, sit down and plan the thing out. Its amazing how these features seem to be tacked on to most modern CMS's IMO none that I have used have gotten the interface for it right, lack decent support, or have gapping holes in the way the system implements it.

Once you have the basics then you can start writing modules and components for it that are "far out".

- Ryan

[ironik]

I read these articles and tried out many CMS systems before attempting to write my own (which is still a WIP). Maybe they may help you:

CMS evaluation:
[steptwo.com.au...]

CMS comparison and evalution (gives you an idea of what features people look for):
[cmsmatrix.org...]

Evaluate other CMS's in one location:
[opensourcecms.com...]

And this one is gold, hands down the best write up I've read on creating CMS's:
[adaptivepath.com...]

[hiker_jjw]

I tend to write my own basic CMS systems for Web site and then include a WYSIWYG editor, such as the FCK Editor, to allow the user to modify the content. Keep it simple.

[thing3b]

The biggest aim for me is to reduce the reliance most CMSs have on WYSIWYG editors (making a WYSIWYG editor more like just an option). I really do not think that browser WYSIWYGs do a fantastic job.

Browser WYSIWYGs should have features like autosaving (done via an iframe)

I could have the whole site created in a WYSIWYG like dreamweaver, but;
- I need the data to be easily created as XML
- I apply XSLTs
- I am an info-maniac and want to collect as much data as possible. For example, if my spell checker says that I have a word wrong and I correct it, I want this correction data stored

On a side note, has anyone seen a semi prolog like implementation using PHP Objects?

[ironik]

You've got a difficult task ahead trying to make your CMS usuable for people with no HTML knowledge. I think that having the WYSIWYG editor is necessary if you want to reach the widest audience. Not sure if you perhaps had an alternative in mind though...?

[Hanu]

My biggest issue: Presentiation vs. Content

Some CMSs have a quick and dirty way to add unstructured content including presentation. Drupal, for example let's you add raw html or php code into nodes. That way it relies completely on CSS for the separation of content and presentation. In fact, Drupal has little structuring of content beyond the page level in general. For small sites this is ok. For big sites it is not. And all big sites once started out small, meaning that at some point these sites needed to switch CMS.

Other CMSs like Typo3 and a believe Mambo structure content at the paragraph level and make it hard to quickly throw in raw html or php.

I suggest you offer both. That way users can start small (quick and dirty) and later structure the content as their sites grow.

[thing3b]

I have tried to design the cms so that any class can spit out what it wants on any page of the site.

I was thinking that I could allow the user to add as many;
- WYSIWYG editors
- "php markdown" areas
- plain text areas
- php code scripts
as they wanted to a single page. I could then leave it up to them and also allow them to set a default.

[RyanM]

With regards to in browser WYSIWYGS alot of processing has to go within PHP to make them HTML efficient. espeacially if you want to make it cross browser, with the different markup that different browsers generate.