Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP
Fetching contributors…

Cannot retrieve contributors at this time

411 lines (276 sloc) 21.857 kB

Tutorial 1 - Building a Basic Site

Overview

Welcome to the first in this series of tutorials on the SilverStripe Content Management System (CMS).

These tutorials are designed to take you from an absolute beginner to being able to build large, complex websites with SilverStripe. We assume to begin with, that you have some XHTML, CSS and PHP knowledge. This first tutorial provides an absolute introduction to building a simple website using SilverStripe. It will also teach you how to use the content management system at a basic level.

What are we working towards?

We are going to create a site in which all the content can be edited in the SilverStripe CMS. It will have a two-level navigation system, which will be generated on the fly to include all pages you add in the CMS. We will use two different templates - one for the home page, and one for the rest of the site.

Installation

You need to download the SilverStripe software and install it to your local machine or to a webserver.

For more infomation about installing and configuring a webserver read the Installation instructions and videos.

This tutorial uses the SilverStripe CMS default theme 'Simple' which you will find in the themes folder. We will investigate the existing template files that make up the theme as well as create some new files to build upon the theme.

Exploring the installation

After installation, open up the folder where you installed SilverStripe.

If you installed on windows with WAMP, it will likely be at c:\wamp\wwww. On Mac OS X, using the built in webserver, it will be in your sites directory /Sites/ (with MAMP, it will likely be at /Applications/MAMP/htdocs/)

Let's have a look at the folder structure.

| Directory | | Description | | --------- | | ----------- | | assets/ | | Contains images and other files uploaded via the SilverStripe CMS. You can also place your own content inside it, and link to it from within the content area of the CMS. | | cms/ | | Contains all the files that form the CMS area of your site. It’s structure is similiar to the mysite/ directory, so if you find something interesting, it should be easy enough to look inside and see how it was built. | | framework/ | | The framework that builds both your own site and as the CMS that powers it. You’ll be utilizing files in this directory often, both directly and indirectly. | | mysite/ | | Contains all your sites code (mainly PHP) | | themes/ | | Combines all images, stylesheets, javascript and templates powering your website into a reusable "theme" |

When designing your site you should only need to modify the mysite, themes and assets folders. The rest of the folders contain files and data that are not specific to any site.

Using the CMS

User Interface Basics

The CMS is the area in which you can manage your site content. You can access the cms at http://localhost/your_site_name/admin (or http://yourdomain.com/admin if you are using you own domain name). You will be presented with a login screen. Login using the details you provided at installation. After logging in you should see the CMS interface with a list of the pages currently on your website (the site tree). Here you can add, delete and reorganize pages. If you need to delete, publish, or unpublish a page, first check "multi-selection" at the top. You will then be able to perform actions on any checked files using the "Actions" dropdown. Clicking on a page will open it in the page editing interface pictured below (we've entered some test content).

  1. This menu allows you to move between different sections of the CMS. There are four core sections - "Pages", "Files", "Users" and "Settings". If you have modules installed, they may have their own sections here. In this tutorial we will be focusing on the "Pages" section.
  2. The breadcrumbs on the left will show you a direct path to the page you are currently looking at. You can use this path to navigate up through a page's heirarchy. On the left there are tabs you may use to flick between different aspects of a page. By default, you should be shown three tabs: "Content", "Settings", and "History".
    • Content - Allows you to set the title, wysiwyg content, URL and Meta data for your page.
    • Settings - Here you set the type of page behavior, parent page, show in search, show in menu, and who can view or edit the page.
    • History - This allows you to view previous version of your page, compare change and revert to previous version if need be.
  3. Within the "Pages" section (provided you are in the "Content", or "Settings" tab) you can quickly move between pages in the CMS using the site tree. To collapse and expand this sidebar, click the arrow at the bottom. If you are in the history tab, you will notice the site tree has been replaced by a list of the alterations to the current page.

  4. This section allows you to edit the content for the currently selected page, as well as changing other properties of the page such as the page name and URL. The content editor has full WYSIWYG abilities, allow you to change formatting and insert links, images and tables.
  5. These buttons allow you to save your changes to the draft copy, publish your draft copy, unpublish from the live website or remove a page from the draft website. The SilverStripe CMS workflow stores two copies of a page, a draft and a published one. By having separate draft & published copies, we can preview draft changes in the site before publishing them to the live website. You can quickly preview your draft pages without leaving the CMS by clicking the "Preview" button.

Try it

There are three pages already created for you - "Home", "About Us" and "Contact Us", as well as a 404 page. Experiment with the editor - try different formatting, tables and images. When you are done, click "Save Draft" or "Save & Publish" to post the content to the live site.

New pages

To create a new page, click the add new button above the site tree.
When you create a new page, you are given the option of setting the structure of the page (Top level or Under another page) and the page type. The page type specifies the templates used to render the page, the fields that are able to be edited in the CMS, and page specific behavior. We will explain page types in more depth as we progress; for now, make all pages of the type "Page".

SilverStripe's friendly URLs

While you are on the draft or live SilverStripe site, you may notice the URLs point to files that don't exist, e.g. http://localhost/contact or http://yourdomainname.com/about-us etc. SilverStripe uses the URL field on the Meta-Data tab of the Edit Page -> Content section to look up the appropriate page in the database.

Note that if you have sub-pages, changing the Top level URL field for a page will affect the URL for all sub-pages. For example, if we changed the URL field "/about-us/" to "/about-silverstripe/" then the sub-pages URLs would now be "/about-silverstripe/URL-of-subpage/" rather than "/about-us/URL-of-subpage/".

When you create a new page, SilverStripe automatically creates an appropriate URL for it. For example, About Us will become about-us. You are able to change it yourself so that you can make long titles more usable or descriptive. For example, Employment Opportunities could be shortened to jobs. The ability to generate easy to type, descriptive URLs for SilverStripe pages improves accessibility for humans and search engines.

You should ensure the URL for the home page is home. By default, SilverStripe loads the page with the URL home.

Templates

All pages on a SilverStripe site are rendered using a template. A template is an HTML file augmented with special control codes. Because of this, you can have as much control of your site’s HTML code as you like.

Every page in your site has a page type. We will briefly talk about page types later, and go into much more detail in tutorial two; right now all our pages will be of the page type Page. When rendering a page, SilverStripe will look for a template file in the simple/templates folder, with the name <PageType>.ss - in our case Page.ss.

Open themes/simple/templates/Page.ss. It uses standard HTML apart from these exceptions:

<% base_tag %> is replaced with the HTML base element. This ensures the browser knows where to locate your site's images and css files.

$MetaTitle, $Title, and $SiteConfig.Title in the html tag are replaced by the title set in the Meta tags, Page Name, or Settings -> Site Title.</p> <p><em>$Title</em> is simply replaced with the name of the page ('Page name' on the 'Main' tab in the editor).</p> <p><em>$MetaTags</em> adds meta tags for search engines, as well as the page title ('Title' on the 'Meta-data' tab in the editor). You can define your metatags in the meta-data tab off the content editor in the CMS. </p> <p><em>$Layout</em> is replaced with the contents of a template file with the same name as the page type we are using. </p> <p>Open <em>themes/simple/templates/Layout/Page.ss</em>. You will see more HTML and more SilverStripe template replacement tags and variables.</p> <p><em>$Content</em> is replaced with the content of the page currently being viewed. This allows you to make all changes to your site's content in the CMS.</p> <p>These template markers are processed by SilverStripe into HTML before being sent to your browser and are formatted either with a <em>$</em> at the beginning or are between the SilverStripe template tags <em><code><% %></code></em>.</p> <p><strong>Flushing the cache</strong></p> <p>Whenever we edit a template file, we need to append <em>?flush=all</em> onto the end of the URL, e.g. http://localhost/home/?flush=all. SilverStripe stores template files in a cache for quicker load times. Whenever there are changes to the template, we must flush the cache in order for the changes to take effect.</p> <h2>The Navigation System</h2> <p>We are now going to look at how the navigation system is implemented in the template. </p> <p>Open up <em>themes/simple/templates/Includes/Navigation.ss</em></p> <p>Menu for our site are created using a <strong>loop</strong>. Loops allow us to iterate over a data set, and render each item using a sub-template. The <strong>loop</strong> <em>Menu(1)</em> returns the set of the first level menu items. We can then use the template variable <em>$MenuTitle</em> to show the title of the page we are linking to, $Link for the URL of the page and $LinkingMode to help style our menu with CSS (explained in more detail shortly).</p> <blockquote> <p>$Title refers to <em>Page Name</em> in the CMS, whereas $MenuTitle refers to (the often shorter) <em>Navigation label</em></p> </blockquote> <pre><code>:::ss <ul> <% loop Menu(1) %> <li class="$LinkingMode"> <a href="$Link" title="$Title.XML">$MenuTitle.XML</a> </li> <% end_loop %> </ul> </code></pre> <p>Here we've created an unordered list called <em>Menu1</em>, which <em>themes/simple/css/layout.css</em> will style into the menu. Then, using a loop over the page control <em>Menu(1)</em>, we add a link to the list for each menu item. </p> <p>This creates the navigation at the top of the page:</p> <p><img src="_images/tutorial1_menu.jpg" alt=""></p> <h3>Highlighting the current page</h3> <p>A useful feature is highlighting the current page the user is looking at. We can do this with the template variable <em>$LinkingMode</em>, mentioned earlier. <em>$LinkingMode</em> returns one of three values:</p> <ul> <li> <em>current</em> - This page is being visited</li> <li> <em>link</em> - This page is not currently being visited</li> <li> <em>section</em> - A page under this page is being visited</li> </ul> <blockquote> <p>For example, if you were here: "Home > Company > Staff > Bob Smith", you may want to highlight 'Company' to say you are in that section. If you add $LinkingMode to your navigation elements as a class, ie: :::ss <li class="$LinkingMode"> <a href="$Link" title="$Title.XML">$MenuTitle.XML</a> </li></p> </blockquote> <p>you will then be able to target a section in css (<em>simple/css/layout.css</em>), ie: :::ss .section { background:#ccc; } You may also style the link to the current page this way, eg: :::ss<br> .current { /* Your styles here */ } </p> <h2>A second level of navigation</h2> <p>The top navigation system is currently quite restrictive. There is no way to nest pages, we have a completely flat site. Adding a second level in SilverStripe is easy. First (if you haven't already done so), let's add some pages. </p> <p>The "About Us" section could use some expansion. </p> <p>Select "Add New" in the Pages section, and create two new pages nested under the page "About Us" called "What we do" and "Our History" with the type "Page". </p> <p>You can also create the pages elsewhere on the site tree, and drag and drop the pages into place. </p> <p>Either way, your site tree should now look something like this:</p> <p><img src="_images/tutorial1_2nd_level-cut.jpg" alt=""></p> <p>Great, we now have a hierarchical site structure, let's now look at how this is created and displayed in our template.</p> <p>Adding a second level menu is very similar to adding the first level menu. </p> <p>Open up <em>/themes/simple/templates/Includes/Sidebar.ss</em> template and look at the following code:</p> <pre><code>:::ss <ul> <% loop Menu(2) %> <li class="$LinkingMode"> <a href="$Link" title="Go to the $Title.XML page"> <span class="arrow">&rarr;</span> <span class="text">$MenuTitle.XML</span> </a> </li> <% end_loop %> </ul> </code></pre> <p>This should look very familiar. It is the same idea as our first menu, except the loop block now uses <em>Menu(2)</em> instead of <em>Menu(1)</em>. As we can see here, the <em>Menu</em> control takes a single argument - the level of the menu we want to get. Our css file will style this linked list into the second level menu, using our usual <em>$LinkingMode</em> technique to highlight the current page.</p> <p>To make sure the menu is not displayed on every page, even those that <em>don't</em> have any nested pages. We use an <strong>if block</strong>. Look again in the <em>Sidebar.ss</em> file and you will see that the menu is surrounded with an <strong>if block</strong> like this:</p> <pre><code>:::ss <% if Menu(2) %> ... <ul> <% loop Menu(2) %> <li class="$LinkingMode"> <a href="$Link" title="Go to the $Title.XML page"> <span class="arrow">&rarr;</span> <span class="text">$MenuTitle.XML</span> </a> </li> <% end_loop %> </ul> ... <% end_if %> </code></pre> <p>The if block only includes the code inside it if the condition is true. In this case, it checks for the existence of <em>Menu(2)</em>. If it exists then the code inside will be processed and the menu will be shown. Otherwise the code will not be processed and the menu will not be shown.</p> <p>Now that we have two levels of navigation, it would also be useful to include some "breadcrumbs". </p> <p>Open up <em>/themes/simple/templates/Includes/BreadCrumbs.ss</em> template and look at the following code:</p> <pre><code>:::ss <% if Level(2) %> <div id="Breadcrumbs"> $Breadcrumbs </div> <% end_if %> </code></pre> <p>Breadcrumbs are only useful on pages that aren't in the top level. We can ensure that we only show them if we aren't in the top level with another if statement.</p> <p>The <em>Level</em> page control allows you to get data from the page's parents, e.g. if you used <em>Level(1)</em>, you could use: :::ss $Level(1).Title </p> <p>to get the top level page title. In this case, we merely use it to check the existence of a second level page: if one exists then we include breadcrumbs.</p> <p>Both the top menu, and the sidebar menu should be updating and highlighting as you move from page to page. They will also mirror changes done in the SilverStripe CMS, such as renaming pages or moving them around.</p> <p><img src="_images/tutorial1_menu-two-level.jpg" alt=""></p> <p>Feel free to experiment with the if and loop statements, for example you could create a drop down style menu from the top navigation using a combination of if statements, loops and some CSS to style it. </p> <p>The following example runs an if statement, and a loop on <em>Children</em>, checking to see if any sub-pages exist within each top level navigation item, you will need to come up with your own CSS to correctly style this approach.</p> <pre><code>:::ss <ul> <% loop Menu(1) %> <li class="$LinkingMode"> <a href="$Link" title="$Title.XML">$MenuTitle.XML</a> <% if Children %> <ul> <% loop Children %> <li class="$LinkingMode"> <a href="$Link" title="Go to the $Title.XML page"> <span class="arrow">&rarr;</span> <span class="text">$MenuTitle.XML</span> </a> </li> <% end_loop %> <ul> <% end_if %> </li> <% end_loop %> </ul> </code></pre> <h2>Using a different template for the home page</h2> <p>So far, a single template layout <em>Layouts/Page.ss</em> is being used for the entire site. This is useful for the purpose of this tutorial, but in a finished website we can expect there to be several page layouts.</p> <p>To illustrate how we do this, we will create a new template for the homepage. This template will have a large graphical banner to welcome visitors.</p> <h3>Creating a new page type</h3> <p>Earlier we stated that every page in a SilverStripe site has a <strong>page type</strong>, and that SilverStripe will look for a template, or template layout, corresponding to the page type. Therefore, the first step when switching the homepage template is to create a new page type.</p> <p>Each page type is represented by two php classes: a <em>data object</em> and a <em>controller</em>. Don't worry about the details of page types right now, we will go into much more detail in tutorial two.</p> <p>Create a new file <em>HomePage.php</em> in <em>mysite/code</em>. Copy the following code into it:</p> <pre><code>:::php <?php /** * Defines the HomePage page type */ class HomePage extends Page { static $db = array( ); static $has_one = array( ); } class HomePage_Controller extends Page_Controller { } </code></pre> <p>Every page type also has a database table corresponding to it. Every time we modify the database, we need to rebuild it. We can do this by going to <a href="http://localhost/dev/build?flush=1">http://localhost/dev/build?flush=all</a> (replace <em>localhost</em> with your own domain name if applicable). </p> <p>It may take a moment, so be patient. This add tables and fields needed by your site, and modifies any structures that have changed. It does this non-destructively - it will never delete your data.</p> <p>As we have just created a new page type, SilverStripe will add this to the list of page types in the database.</p> <h3>Changing the page type of the Home page</h3> <p>After building the database, we can change the page type of the homepage in the CMS. </p> <p>In the CMS, navigate to the "Home" page and switch to the "Settings" tab. Change "Page type" to <em>Home Page</em>, and click "Save & Publish".</p> <p><img src="_images/tutorial1_homepage-type.jpg" alt=""></p> <p>Our homepage is now of the page type <em>HomePage</em>. However, even though it is of the <em>HomePage</em> page type, it is still rendered with the <em>Page</em> template. SilverStripe still renders the homepage using the <em>Page</em> template because when we created the <em>HomePage</em> page type, we inherited from <em>Page</em>. So when SilverStripe cannot find a <em>HomePage</em> template, it will use the <em>Page</em> template. SilverStripe always attempts to use the most specific template first, and then falls back to the template of the page type's parents.</p> <h3>Creating a new template</h3> <p>To create a new template layout, create a copy of <em>Page.ss</em> (found in <em>themes/simple/templates/Layouts</em>) and call it <em>HomePage.ss</em>. If we flush the cache (<em>?flush=all</em>), SilverStripe should now be using <em>HomePage.ss</em> for the homepage, and <em>Page.ss</em> for the rest of the site. Now let's customize the <em>HomePage</em> template. </p> <p>First, remove the breadcrumbs and the secondary menu by removing: <% include SideBar %> we don't need it for the homepage. </p> <p>Let's replace the title with an image. Find this line: :::ss <h1>$Title</h1></p> <p>and replace it with:</p> <pre><code>:::ss <div id="Banner"> <img src="http://www.silverstripe.org/themes/silverstripe/images/sslogo.png" alt="Homepage image" /> </div> </code></pre> <p>Your Home page should now look like this:</p> <p><img src="_images/tutorial1_home-template.jpg" alt=""></p> <p>SilverStripe first searches for a template in the <em>themes/simple/templates</em> folder. Since there is no <em>HomePage.ss</em>, it will use the <em>Page.ss</em> for both <em>Page</em> and <em>HomePage</em> page types. When it comes across the <em>$Layout</em> tag, it will then descend into the <em>themes/simple/templates/Layout</em> folder, and will use <em>Page.ss</em> for the <em>Page</em> page type, and <em>HomePage.ss</em> for the <em>HomePage</em> page type. So while you could create a HomePage.ss in the <em>themes/simple/templates/</em> it is better to reuse the navigation and footer common to both our Home page and the rest of the pages on our website.</p> <p><img src="_images/tutorial1_subtemplates-diagram.jpg" alt=""></p> <h2>Summary</h2> <p>So far we have learnt about template variables, controls and if statements. We have used these to build a basic but fully functional website. We have also briefly covered page types, and looked at how they correspond to templates and sub-templates. Using templates, we have customized our website's design according to the page type of any given page.</p> <p>In the next tutorial, <a href="2-extending-a-basic-site">Extending a Basic Site</a>, we will explore page types on a deeper level, and look at customising our own page types to extend the functionality of SilverStripe.</p> <p><a href="2-extending-a-basic-site">Next Tutorial >></a></p> <h2>Books on SilverStripe</h2> <ul> <li> <a href="http://www.silverstripe.org/silverstripe-book">Official book on SilverStripe in English</a>.</li> <li> <a href="http://www.silverstripe.org/das-silverstripe-buch">Official book on SilverStripe in German</a>.</li> </ul> <p><img src="_images/silverstripe-cms-book-front-cover-design-june2009preview.jpg" alt=""></p>

Jump to Line
Something went wrong with that request. Please try again.