Frequently Asked Questions
How can I make a site like the PeepCode blog, with a different design on every page?
Geoffrey Grosenbach customised an earlier version of Nesta, as described in his excellent write up on the PeepCode blog.
Nesta now has a blogazine plugin that is designed to help you achieve the same thing. It’s documented in the Making an Art Directed blog recipe.
There are lots of CMS’s and blog engines around – why write another?
There were several reasons. In no particular order:
- I enjoyed it.
- I was sick of editing articles by copying and pasting text from my text editor into a web browser.
- I was really sick of Mephisto’s seemingly random decisions to mark lots of articles as new in my Atom feed when all I’d done was fix a typo in my latest article.
- I wanted to be able to write content that wasn’t automatically included in my feed (category pages never show up, and articles only show up if you set their date).
- I wanted to be able to apply Mark Nunney’s excellent SEO techniques (see point number 10, and his article on website structure) without resorting to a big system like Drupal.
When I update an article it isn’t republished to the Atom feed. Can I force it?
No, you can’t. One of my main irritations with other CMS’s or blog engines was that changes to an article could cause the article to be republished in my feed. This made me reluctant to fix typos or improve an article’s text, in case I spammed people who followed my RSS feed with minor updates.
Guaranteeing that an article would never be re-listed in the Atom feed was a design goal.
The only time an article will re-appear in the feed is if you rename the file on disk (i.e. give it a new permalink). You can prevent a renamed article from being re-published in the Atom feed by specifying the article’s Atom ID (setting it to the original value – see the “Atom ID” section of the metadata reference for details).