Architecting a site with Movable Type

Once you get the Movable Type wizard to run, or build the mt/mt-config.cgi file, you can architect your site. Unlike most programmers, humans can think in two dimensions, so you are best off using a piece of paper and a pen.
The great thing about Movable Type's static publishing paradigm is that nothing is written to your site until you click on a "publish" button in the Movable Type program on your browser. So this made it ideal to add alongside my existing rako.com website, and then slowly create pages until the whole site is controlled by Movable Type. This meant that my architecture had to provide for existing content. There was going to be some content that would be redone in a different location but you should never ever take down any web page. You can change it to show where the new version is, but don't just delete it.

I like designing things on B-size, also called ledger size paper. Staples has nice 11x17 graph paper. The first task was to draw up the structure of the existing rako.com site.
Rako.com_existant.jpg
It took several re-draws, but I eventually came up with a decent design for rako.com.
Rako.com_proposed.jpg
The proposed drawing shows that there will be 8 "blogs" in site. That does not mean 8 idiots blithering about their cats. It means there will be 8 sub-directories with their own index page, archive page (what MT calls "contents") and its own style-sheet. The "Masthead" and "Contents" sub-directories will be created by the root website install of movable type. Each blog in a MT website is given a number by the software when you create it. MT must us ID=1 for he root website, since the first blog I created, "Archive" was given blog ID #2. So I had to bump all the numbers by one as I created each of the 8 blogs and 8 subsequent sub-directories.

On the right side of the page I mapped the blog names to a sub-directory, keeping the name as short as possible. I use capitalization in sub-directories to improve readability of the URL (Uniform Resource Locator). At the bottom right I account for mapping old content into the new structure. You can see I was once stupid enough to have a space on the URL with "Other Voices". You can also see I left those pages up but replicated them in a directory "Other_Voices". I will put that content in one of the new sub-directories but I will leave both of those old sub-directories on the web server so any traffic Google drive to them will not get dead-ended to a 404 page.

[Update] After creating the 8 blogs called out in the above drawing, I decided it would be nice if the Masthead was a blog instead of a page created by the root site engine. My thinking was that I could make an entry for each person that helped me or taught me something. Then the Masthead/index.html pages would be the roll-up of those people. I could also have a Contents html page if I desire to separate the contributors by category, family, friend, author, boss, protege etc. So after populating and entry or two in all the blogs except Archive, I added a Masthead blog that I can put down my influences.

About this Entry

This page contains a single entry by Paul Rako published on May 15, 2011 2:09 AM.

Installing Movable Type 5 OS was the previous entry in this blog.

Blog settings in Movable Type is the next entry in this blog.

Find recent content on the main index or look in the archives to find all content.