The Movable Type and Professional Network Wiki has been moved to wiki.movabletype.org.

Arvind Satyanarayan

[Login] Change #6 by Arvind Satyanarayan at 2007-01-28 18:13:30.

MT 4.0 Ideas

3.Make it easier to manage complete sites with Movable Type

I believe it was Tim who first elaborated on the Pages idea but my take on it would be like so:

a Master template (perhaps system so it cannot be deleted) which can contain anything but must contain a tag, say MTContent, that will be populated as appropriate for each Page. Thus, you can have anything common to your pages - header, sidebar, footer - and only need to place one tag for content.
A Pages section to the app (both listing and new) which should be extremely similar to Entries. The New Page screen should function similar to New Entry with title, content and text formatter options - so we can essentially just type out content without worrying about markup, layout etc.
On creating a new Template a prompt to ask whether you would like to start with the Master

Easier upgrade process. I've got MT checked out of svn so my upgrade is essentially an svn up. However, for the vast majority of people, upgrades mean reuploading everything from the distribution and with a more frequent release cycle, this could fast become painful (see Wordpress!)
Wishful thinking perhaps but a Textmate snippets like functionality for container tags would be awesome. For example MTEntries and tabbing through the various attributes.
Author Archiving. See my ideas on implementation in CustomFields 2.0b1. Nothing terribly different from the current archive types except the default context is an author.
I'm not sure if this is even possible but on enabling/disabling plugins when running under FastCGI, restart the process?

[Login] Change #6 by Arvind Satyanarayan at 2007-01-28 18:13:30.