What you like/dislike about CMSs

[Liquid-Fire]

I am right now im my spare time aprat from my job and other programming project am designing a CMS. I plan to develop it using PHP5 and MySQL5. I am doing this becuase I know there are alot of other CMS's out there but I can seem to find one that I like so I have desided to design one from scratch. Here is a list, some are broad in what they will intial, of feature I am going to be designing for my CMS:

Major Features Needed To Be Designed:


* Admin System/Panel
* Menu Editor( part of Admin System )
* News System
* New Categories( part of News System )
* Front Page( part of News System )
* Download System
* Screen Shot System
* Forum System( may design to incorporate VBulletin )
* User System
* User Groups( part of User System )
* Template System
* Asset Manager
* Project Management Tool( Used as Online help, but scale so can be used to mantain custom project )
* Bug Tracker/Tracking( part of Project Management Tool )
* Intergrate A Wiki System( Thinking of MediaWiki right now )
* Allow for Custom Inputs( example: You can use the download system to create a tutorial download and maybe you would want to have a custom input like diffculty Level which is not part of the download system becuase not every download is going to have a diffculty level )
* Independent on file naming( example: If you wanted the new to link to a page with the name htgdfebr.php it could, have it easliy changed inside the Admin Panel, not having to go into the code )



One major thing I want to try in incorperate with the CMS is that ALMOST EVERTHING can be change within the CMS admin panel.

Now with User System, News System, Download System, etc... will all have Add/Delete/Edit features and want not. Now what I would like from you guys and some input on what you would like to se in a CMS, what you don't want to see in a CMS, stuff like that. I will be taking any feedback into consideration, I mean if you want a feature that lets you ping an address( sorry but can't think of something really dumb to have in a CMS ), I will most likely not include it in the design process. Thank for you input, for those of you that give it of course.

Thank You,
Ryan Zec

[Rappa]

one of the things i hate about some cms is that they use their name in the urls. which makes me not want to use them.

for example:

an e107 link

http://www.yoursite.com/e107_plugins/this.php

id rather it be:

http://www.yoursite.com/plugins.php?id=plugin

know what i mean?

[chump2877]

AJAX, anything AJAX :D

Seriously, anything to speed up a web application enough so that it is comparable in speed to non-web applications...

[Rich Pedley]

depending on what it is used for but the following have all been requested in the past:

form generator
polls
membership system
integrated shop
versioning (of changes to pages)
dublin core
If you have an automatic menu system, then amending the order of the links.
admin image gallery
public gallery
latest page changes
latest news with rss feed
upcoming events
newsletters

s'nuff for now :-)

[Mhtml]

Well, I myself have been creating a CMS for probably close to a year. I recommend going completely modular. Technically, it's not a CMS what I've built. It's more of a framework and everything else is just a plugin. The one thing I hate about most CMS' is that they all look the same and feel the same. However I like modular systems, very modular...Everything should be a module and removable down to the framework, I like power!

[degsy]

Forum System( may design to incorporate VBulletin )
Sounds expensive ;)

[Kurashu]

One thing that I'd like to see in more CMS (CMSes?) is a built in page editor for the CMS. Maybe protect some key files, add some backup functionality, an auto-update function (stores changes in the database, and then updates the changed pages at say midnight or whenever, and then empty the table).

That way you can add any functionality you want at any time.

[fci]

One thing that I'd like to see in more CMS (CMSes?) is a built in page editor for the CMS. Maybe protect some key files, add some backup functionality, an auto-update function (stores changes in the database, and then updates the changed pages at say midnight or whenever, and then empty the table).

That way you can add any functionality you want at any time.

use your own combination of scp/rsync/ssh/mysqldump to do backups. i suppose an interface could be made from php to give instructions to the cron script but that's only a small part of it.


rather then re-inventing the wheel entirely, I'd recommend taking a look at some of the PEAR modules out there, mainly pear::HTML_quickform and pear::DB .. and then also take a look php savant for doing templates. you did say you wanted to do it from scratch but.. eh.

[Liquid-Fire]

for the person who commented on vBulletin, true I want to support it since i have it, but it would not be required, you would just not have intergrated forums unless you developed a plugin for you own forums system or i desided to develop one myself.