doc/guides/html/designer_guide.html in browsercms-3.0.1 vs doc/guides/html/designer_guide.html in browsercms-3.0.2

- old
+ new

@@ -136,10 +136,20 @@ <li>How to create custom page templates</li> <li>How to create custom page partials</li> <li>How to use helpers to add dynamic content to templates and partials</li> <li>How to use the <span class="caps">CMS</span>-specific form builder extensions</li> </ul> - + <h2>Creating a template +Each page in BrowserCMS uses a single template, which is designed to provide overall layout structure of the page. Here&#8217;s the general process +that a design team might follow to create a <span class="caps">CMS</span> template.</h2> +<p>1. Start with a <span class="caps">PSD</span> or <span class="caps">JPG</span> of the design, which represents the end result of what the webpage should look like. +2. Create a static html file which implements that design. +3. When creating menus, use the same structural <span class="caps">HTML</span> markup as will be generated by the Menu <span class="caps">API</span>. (See Menu&#8217;s below) +4. Change the file extension from .htm to .html.erb and add it as a template to the <span class="caps">CMS</span>.</p> +<h2>Menus +BrowserCMS provides an <span class="caps">API</span> to allow menus to be dynamically generated based on the sitemap. The purpose of this is to make +it easy to add new pages, without having to modify templates.</h2> +<div class="code_container"><code class="ruby">render_menu</code></div> </td> </tr> </table> </div> </div>