/bigtopic
/bigtopic/moregranulartopicthatisstillunderbigtopic

On a related note, with your Smarty tutorial, you pointed me down that path and now my entire site is Smarty templates.

One thing I will say is that I don't like the idea of having to create a category for every directory (or sub-directory) I want to write to especially for client work, since that is non-intuitive and frankly a pain in the butt. However, the alternative of having the client's main About page come up in the search with the title /about/index is just Plain Ugly.

I think that the way that I would do it would be to use the title for the proper page title and the EntryMore field for the whole path to the file. Sure it could be used for storage or something else, but it's not as semantically useful as say the keywords or excerpt fields....

Anyhow, thanks for putting this out there. I is a great idea.

I wanted to provide student organizations at my institution an easy way to manage their content. I set things up exactly in this manner last winter -- and am rolling it out to them this fall.

Cool. Now I can add this! And thanks for all you do!

field1=foobar
field2=the quick brown fox

You can then either apply some nifty MTPerl (thanks to Brad), or you can do what I do and throw the fields around the title, the header, the meta tags, various points of navigation or wherever you need it.

I discuss the PHP solution to some degree on my own blog, though the code is very Perl-ish.

I'll give this a spin, though.

Not so new. :( Though, here's what I did that's a little different.

My content is both static and bloggish. In other words, while using so-called static content like an about page, I allow comments on everything so that people can basically leave whatever comments about that page they like. On my about page, though no one has done it because I'm low-traffic, someone could ask a life question or something and I could answer there. Just a variation.

Also, I use categories for sections/directories and category indexes for the index.php page. Thus a summary of that category. It's in-between static and dynamic, really, but it's zero-maintenance.

Some pointers. :)

I have a large number of content managers who don't even want to look at the MovableType admin screens so I've made something that looks like a Bookmarklet that brings up the blog description, allows users to edit it, and rebuilds the site on saving changes. Then they can refresh the page and voila! - the changes they just made to the static content are instantly published.

The only catch to this is that searches on the site only work across blog entries, so all the static content is ignored. Does someone have a nifty hack to have the search run across entries and descriptions? (I've posted to the MT support tips & tricks forum on this issue too... http://www.movabletype.org/support/index.php?act=ST&f=14&t=24344 )

My module looks like:

<MTMacroDefine name="smile1" string=": )"><img src="<$MTBlogURL$>static/emoticons/smile.gif" width="15" height="15" alt="[image: emoticon-smile]" /></MTMacroDefine><MTMacroDefine name="smile2" string=": -)">

I also referenced http://www.thegirliematters.com/tips/archives/0209/smilies_with_mtmacro.php as I tinkered, who seems to be able to have all her emoticons in one module, whereas I cannot. Puzzling..

I'm using the default MT template, the emoticon module is the only augmentation. I use apply_macros="1" within the MTEntryBody and MTEntryMore tags. Is there something else I need to include?

Thank you so much for a really interesting script. :)

Any help in this regard would be greatly appreciated :)

Thanks,
Matt

.html

on the archiving page. I currently keep my static content in flat files that get wrapped in a format via Perl scripts so I should be able to create an input file to load into Movable Type.

Thanks for documenting this method.

I want the static index page in the root directory to contain every link to the index page of each sub-domain. It is THERE in each sub-domain that blogs are posted and searched. Yep, 50 blogs, so far, each posted by pre-selected clients who log-in with password protection. Latest news, specials, sales, changes of schedule, public announcements.

I have read the "Doing your whole site in MT" info on deleting index templates, and almost all the archive templates, etc. Brad, given my desired scenario, is there anything to add or modify about your instructions? Any caveats?

And does managing this many sub-domain blogs sound gargantuan?

Feeling mighty Lost and mighty MT