If you’re sick to death of reading about this stuff, just skip this article. I’m updating the GhostHouse site so it’s based on MT.
Summary:
I went with the “one individual archive per entry” model and generated the content for every kind of article in every archived article page. Then I split the contents into DIV entities and wrote CSS to only show the appropriate content for that page.
- First we have to Future-proof MT.
This also hides the implementation of individual archives from the casual viewer. So far I just changed everything to an “index.html” (one file per directory) and didn’t complete the rest of the conversions. - Make a monster template for the “individual archive” pages containing the HTML for an article of every type of category.
- Specify the CSS for a given page based on the category name, in addition to the “General” CSS file.
- For the general CSS, strip out all the design-type elements and move them into the individual category CSS
- In the CSS for each category, make the inappropriate entities (HTML which appears in only articles which are not in this category) invisible
- for the crew pages, generate (as a template) a .htaccess file which specifies by name every crew article
- also nazi all the “link only” pages. Thus, we generate them, but no one will ever see them
- since the “crew hub” really is more like an announcement page, we need an archive of that… but if we use a vanilla monthly archive it will show the things on the main site as well. So, we make a monthly archive template which only shows the “crew-only” content, including the links.
- We don’t really need monthly main-site pages- since entries are not updated on a timely basis, it would be meaningless. Instead, we make a big archive of all the “In Production” and “Now Showing” movies, as index page templates.
- We need two calendar pages- the main site’s “Screening Calendar” and the crew-only “Production Calendar”