Pages of these types are Sheets.
Sheets have an option to output paths with a cache parameter which will create a digest of the rendered content.
true the paths output from the
where the parameter is created from the rendered content of the sheet.
Without this set, the paths will be:
and the pages will not be rendered to generate the path.
The basic features:
- set a longer expire time for Sheet content with
sheet_cache_timeout(similar to the typical
cache_timeoutset for pages)
- provide Radius tags to output content as it is, as a link to content, and as an HTML element containing the content
- append a timestamp to sheet content URLs so that the cache need not be cleared with the same frequency for updates to typical pages
Differences with other solutions and the benefit of using Sheets
Some standard site templates provided by Radiant include stylesheet content in a typical page. This requires a custom layout merely to set the content type, and displays content unintended for editing by typical users. This makes for a cluttered page index view and cluttered layout index view.
You can get around this SNS limitation by using the SNS Page Hook extension but even this solution will lead to unpredictable results because it merely copies modules from the Page model to the TextAsset model and tricks the included methods into believing they are operating on a Page. But this is not a good long-term solution.
Not only does it do all this, but the standard Page model provides a
headers method which Sheets overrides to alter the mime-type for the returned content. Sheets uses the built-in ways to serve content, rather than generating yet another way to serve content like SNS.
Special thanks goes to Chris Parrish for creating the SNS extension in the first place. And thanks to Dane Harrigan for some early bug checking.
Built by Saturn Flyer