-
☆ A M B ☆
- 2,475 Posts
1. Big one for serious "mission critical" use: Trackback. The ability to track the version of a page (or a chunk, or a snippet) back x versions. Expression Engine and some other CMS’s have this built-in. I know some work has been done on this, but it should be incorporated into the core.
2. Widgets are very poorly documented... the ability to add a new Widget easily could be really useful. Either this should be streamlined, or the roll of widgets should be moved over to Snippets entirely... almost everything that is done with a Widget can be accomplished through a little more work in the template or via a Snippet call. Widgets need to be clearly defined... then it’ll be easier to tell if they should be augmented or cut.
3. One really nice feature about some other CMS’s is the ability to define all fields for a type of page (e.g. Expression Engine’s weblogs). Template Variables should probably be called "Custom Fields" instead, and I’d love to see the following:
-- More support for other MySQL data types, e.g. lat./long. coordinantes.
-- A built-in Image field... the user can browse for the image filepath, and the the [*place_holder*] could be parsed with the name, src, AND height and width attributes. The Existing Image Widget doesn’t read the height and width tags, so it’s arguably not any better than an img tag src=[*template_variable*]
Unified use of Snippets could accomplish all of these things, I think... you could have a template variable that allowed you to embed a movie, or a table, etc.
4. Item specific help links... how cool would it be if specific elements of the admin interface had "help" links that took you back to either the official documentation or to the wiki for that particular item? That would be extremely useful to put a documentation/help link RIGHT WHERE the user needs it.
1) check out the content-history plugin, it has great rollback functions and promises to get even better.
2) not sure if I agree about removing widgets. I would like to see them updated and modernized.
3) Having variables tied to templates is a bit odd in my opinion. However how does a template differ from a page type? You could use your own combination of TVs to create interface for adding any file type, and with the help os plugins and snippets you can get virtually any output you want.
4) good idea.
The problem with some CMS that have stuff built in is very often that then there is only one solution
and u end up being like everybody else.
Thanks to modx we all have to learn PHP!
-
☆ A M B ☆
- 2,213 Posts
In addition to history it would be nice to have future so we can update a page and set it to publish at a later date or rebuild a site and have it relaunch at a different date.
Granted the only problem with that is how to view the different versions and/or preview them...
AMDbuilder
In addition to history it would be nice to have future so we can update a page and set it to publish at a later date or rebuild a site and have it relaunch at a different date.
That is possible now is it not? *Trying* Then just put a end date for this page and have a new round the corner...
-
☆ A M B ☆
- 2,213 Posts
Quote from: mrhaw at Nov 14, 2008, 04:56 PM
In addition to history it would be nice to have future so we can update a page and set it to publish at a later date or rebuild a site and have it relaunch at a different date.
That is possible now is it not? *Trying* Then just put a end date for this page and have a new round the corner...
Nope, you can future post a new page, but you can’t future post an existing page. Another way to consider this is a development/staging version of a page.
AMDbuilder
Oh, Got ya!
