If the OPML file has a long title, which you can set using the Set titles command in the File menu, we use that, if it's not empty.
Otherwise we use the text attribute, which can be set via a # directive at the top level (I assume most people using blogHome types have already done this).
Otherwise we set it to the empty string, and there is no text at the top of the page.
And a new macro called <%blogHomeDescription%> which appears just below the title, in italic. It's set to the description set in the Set titles command, if it's present, otherwise the empty string. You can see a demo of it on the home page of the newbie site.
We want to streamline things for people using Fargo to blog.
That restores the default type for the top level to index.
I want comments in the default website, so when I see a user asking questions about how Fargo works, I can easily answer them. However, I don't like that the comments often take up twice as much space as the user's post, even if there are no comments. Most of it is advertising. I don't begrudge them their advertising, but only if the feature is being used, by the reader.
So, by default the comments are now hidable. There's a link with a wedge, in the footer text, that says Show comments. If you click it, the comments are shown and the text changes to Hide comments.
With the feature off, comments are handled as they were prior to this change.
For example, here's a blog post on newbie's site.
The Archive menu is built automatically by the server (it has a type attribute of archive). One month for every month there are blog posts. From there you can view a blogHome rendering of the month. In this special case there is no limit on the number of items, so you get every post for the month.
This is a menu that we can edit at Small Picture, so if you have any suggestions for what a newbie might want here, please chime in.
It no longer sets the font and size, letting the bootstrap theme determine these.
You can change the default by choosing one of the themes from the bootswatch site, and adding this directive at the top level of your site.