Page History

...

• First we will introduce one new db column to the webpage database table named "action". During the upgrade process all existing 'Weblog' templates will be updated to action "weblog" while all other pages will be given action "custom". Then moving forward we can add support for any new actions we need. This will be the only change required in the data model.
  • Templates which are used for specific actions will always have a standardized name, description, and link, so those things cannot be controlled by users. This will behave the same way the current standardized templates (Weblog, _day, _css, _decorator) do, where users may not edit the name, description, or link value for that template.

...

• We can optionally define new Model objects to provide methods which are targeted for use specifically on the various action templates. The best example is how there is a specific SearchResultsModel to be used for displaying search results.
  • We can build on this portion of the design after defining exactly what custom actions will be supported and whether or not those actions would benefit from a custom Model.

...