New Archive command in File menu
If an outline is getting large, you may want to archive pieces of it.
It works by converting a sub-outline into an include.
An advanced feature
Archived material can't be edited
Only archive sections that you don't need to edit, because you won't be able to edit them.
For example, if you're keeping a blog in Fargo, you might want to archive July's posts at the beginning of August -- only if you're sure you won't need to edit them.
Let me say it one more time -- no edits after something is archived.
How to
Put the cursor on the section of the outline you want to archive.
Choose Archive outline from the File menu.
Click OK to the confirmation prompt.
Wait a few seconds.
The bar cursor should change to an include node.
Technical details
The archives are stored in the archive sub-folder of your Fargo folder in Dropbox.
They're stored in a calendar structure and given fairly cryptic names that are very unlikely to "collide" with each other.
RSS feeds strictly chronological
Previously the feed was built by traversing the outline in the order of display. So if the calendar structure appeared first, all the elements in the calendar would be added to the feed before any others.
Now we do it strictly chronologically, so that if you add an item and move it outside of the calendar, it will appear in the feed in the order it was created.
As a result of this change, any item that does not have a created attribute will not appear in the feed.
Comments are now visible by default
I would prefer if reading one of your posts, to be able to view any comments people had left without having to click on the "Show Comments" link. I imagine most others do as well. Previously comments were hidden by default. Now they are visible by default.
If you would prefer that they be hidden, add this to the top level of your outline:
New verb: string.hashMD5
In Fargo 0.98 we introduced the img attribute.
A small addition -- if there's a url attribute on the same headline, we link from the image to that URL.
You can see an example of this in the image of the O'Reilly Bootstrap book on this post.
Background
Luckily, I caught this advisory from Bootswatch about Bootstrap 3.
At some point they're going to switch over to Bootstrap 3 themes in place of the current Bootstrap 2 themes. This is good -- at some point we will probably switch Fargo over to Bootstrap 3 as well. But we will probably always want to have a snapshot of their version 2 themes around, so I just made copies of them and made a change to the core Trex code to generate URLs to our copies instead of theirs. This was always the fair thing to do, there's no reason they should be paying to host files that we're using for our sites, esp since I'm now using a Bootswatch theme for Scripting News.
The change
What you should do
There are two ways to reference the themes, by URL and by name:
It's probably safer, long-term, to use the name instead of the URL.
But for now, either way works.