This post explains how Fargo 2 connects with the naming system.
There are three points of connection, two for the Name Outline command in the File menu, and one for the rendering process in the CMS.
This documentation is here so you can see how the process works. Don't call these endpoints, they're just for Fargo to call. Thanks.
1. Is the name available?
URL: http://namer.smallpicture.com/ajax/isNameAvailable
Param: name, a string
Returns: An HTML snippet suitable for display saying whether the name is available.
2. Grab this name
URL: http://namer.smallpicture.com/ajax/newOutlineName
Params: url of the associated OPML file, name, both strings
Returns: JSON struct indicating whether it worked.
Note: It's a JSONP call, the routine name is getData.
3. This outline updated
URL: http://fargoajaxsupport.smallpicture.com/ajax/pingPackage
Params: url, a string
Returns: Nothing worth looking at (at this time).
Note: The URL is what was returned by the grab this name call. The OPML file must contain a <head> element, linkHosting, that points to a package file. You can see what one looks like in the #hosting folder of the Fargo app folder.
More docs will be forthcoming, for sure.
Starting the transition of Scripting News to the new CMS. Reviewing the original site and what Fargo produces, and hacking at the differences.
I archived the outline for 2013, I'm not going to try to convert anything before 2014. The OPML is preserved and the static web pages are exactly where they belong.
I had already archived the 2013 entries for the Fargo blog in this outline. Again, I'm not re-rendering these pages. They are as they are.
Problem with Render Page command, getPathToBarCursor is not defined. (The name of the routine had changed, but the code did not.)
Took the <h2> title out of the blogHome template. It's not supposed to be there. (Look at the current Scripting News home page, no title.)
A new Overrides panel in the Outline Settings dialog, with one initial item in it, type. You can say what type the + icon in the left margin creates. So globally you could have it be outline, and in just one website it could be a custom type.
The Name Outline command works once again. It now turns on the two rendering preferences in the CMS panel of the Outline Settings dialog. Named outlines that don't render don't make much sense.
I was trying to sort out the various problems with index pages, and realized I had created something too complicated to debug, or to document, or use for that matter.
This is a common trap in developing CMSes. One extra option too many. Even I didn't understand how it worked. (And I didn't want to.)
So I solved the problem the same way we did in Trex...
We once again have a blogHome type and a template to go with it.
As with Trex, put a #type "blogHome" at the top level of your outline.
By default there are 10 items in each blogHome page, but you can change that by setting #blogHomeItemCount.
I've re-rendered the Kim Parker site with the new setup, and you can look at the source to see how it works.
I've also re-rendered the Fargo Docs site, which is the one that makes use of index pages. It was a tweak to those pages that broke the camel's back and made the index type unsuitable for weblog home pages.
Whew!