-
Notifications
You must be signed in to change notification settings - Fork 0
Home
ComfortableMexicanSofa's content management is simple, yet incredibly flexible. Here's how it's done:
| CMS Layout | Cms Page Creation | Final Result |
|---|---|---|
<html>
{{ cms:page:header }}
{{ cms:page:body }}
{{ cms:page:footer }}
</html>
|
[ form field for header ]
[ form field for body ]
[ form field for footer ]
|
<html>
header content
body content
footer content
</html>
|
Step 1: First, a Layout is created. There you define your HTML structure for the page and tags that are used to populate content.
Step 2: Tags that were defined in the Layout dictate what form fields are going to be rendered during Page creation.
Step 3: When rendering a Page, Layout content and Page content (along with everything else) are merged and displayed.
- Tags: Page Tag
- Tags: Field Tag
- Tags: Snippet Tag
- Tags: Helper and Partial Tags
- Layouts: Using Application Layout
- Layouts: Nesting Layouts
- Layouts: CMS managed CSS and JS
- Sites
To upgrade to a newer version of Sofa you must bump up the version number in your Gemfile and run bundle install. After that run rails g cms and if necessary replace css/js/images with newer versions. Sometimes there will be migrations that you'll need to run. They will be found in /db/migrate/upgrades. You'll need to run them in sequence starting with whatever version you're upgrading from.
- Finalizing Mirrored sites functionality
- Implementing 'Shared' resources. Layouts/Pages/Snippets that are exactly the same across all Sites. Will ride on top of Mirrored functionality.
- Replacing tinyMce with wymeditor (very likely)
- Figuring out i18n for mirror sites and hostname/[en|fr|jp]. Maybe Site can be defined as hostname + locale path prefix.
- Making Uploads more useful. Integration with wysiswyg editor and making side widget less useless.
- Adjusting Fixtures functionality to do both import and export. Better rake tasks.
- Taking a look at page caching. Currently it plainly doesn't work with multiple sites.
- Moving images/css/js to app/assets. I guess going Sass way will make it possible to serve css in both Rails 3.1 and 3.0 directly from the engine without moving things to public? Would be nice to get it working before RC gets released.
You if you have any questions feel free to contact me via GitHub or @GroceryBagHead