Tuesday, November 26, 2013 at 10:25 AM

Differences from Trex

The method attribute is not supported

  • Almost all types pass through the Markdown processor now, and there is no rules-based rendering.

  • The exceptions are presentation type and untyped pages. In both cases the CMS generates the structural HTML, and it's not really great to pass it through Markdown.

The <%menu%> macro is now a script macro

  • Use <%menu ()%> instead of <%menu%>.

Macros are supported everywhere they can reasonably be supported

  • I took a much closer look at the rendering process and tested carefully.

  • Glossary elements can now contain macros. This will prove useful.

Includes everywhere

  • I think you can have an include everywhere in the CMS. Not sure they work everywhere though. There are so many places to test.

There are no http macros, httpHost, httpPath, httpUserAgent.

  • There is no server, so these values are not available.

  • However, there is a <%path%> macro that gives you the path to the current page.

The RSS file is no longer stored in the RSS folder

  • It may seem counterintuitive, but the RSS file is now stored in the HTML folder for the outline, along with the other files that make up its website. It needs to be processed in the same way as the HTML files.

The #bootstrapTheme attribute changed

  • It can no longer be a full URL, it has to be one of the names of the themes.

  • So this no longer works:

    • #bootstrapTheme "http://bootswatch.com/readable/bootstrap.min.css"
  • Use this instead:

    • #bootstrapTheme "readable"
  • If you want to replace bootstrap.min.css with your own file, set the cssUrl attribute to point to it.

The archive type in menus is not implemented

  • However there is a new stories type that will give you a menu with the most recent stories in it, in reverse-chronological order. You can set the #maxStoryList attribute to determine the number of stories.

Menu items that contain pages are not implemented

  • In Trex you could put a type attribute on a menu item, and the text under it would be displayed as a page on the site. This is not implemented in the new CMS.

cmsPrefs.opml lets you set global attributes

  • So if you want to define glossary items, for example, that can be accessed in any of your websites, add them to this outline. Explained here.

Last built: Tue, Dec 9, 2014 at 3:29 PM

By Dave Winer, Tuesday, November 26, 2013 at 10:25 AM. Don't slam the door on the way out.