mirror of
https://github.com/silverstripe/silverstripe-framework
synced 2024-10-22 12:05:37 +00:00
Merge pull request #3223 from camfindlay/patch-6
Fixes to the :::ss parsing tutorial 1.
This commit is contained in:
commit
f48cf98921
@ -116,7 +116,7 @@ ensures the browser knows where to locate your site's images and css files.
|
||||
$SiteConfig.Title
|
||||
|
||||
These two variables are found within the html `<title>` tag, and are replaced by the "Page Name" and "Settings -> Site Title" fields in the CMS.
|
||||
|
||||
|
||||
:::ss
|
||||
$MetaTags
|
||||
|
||||
@ -127,7 +127,7 @@ The MetaTags variable will add meta tags, which are used by search engines. You
|
||||
The Layout variable is replaced with the contents of a template file with the same name as the page type we are using.
|
||||
|
||||
Open *themes/simple/templates/Layout/Page.ss*. You will see more HTML and more SilverStripe template replacement tags and variables.
|
||||
|
||||
|
||||
:::ss
|
||||
$Content
|
||||
|
||||
@ -155,7 +155,7 @@ We are now going to look at how the navigation system is implemented in the temp
|
||||
Open up *themes/simple/templates/Includes/Navigation.ss*
|
||||
|
||||
The Menu for our site is created using a **loop**. Loops allow us to iterate over a data set, and render each item using a sub-template.
|
||||
|
||||
|
||||
:::ss
|
||||
<% loop $Menu(1) %>
|
||||
|
||||
@ -278,7 +278,7 @@ Breadcrumbs are only useful on pages that aren't in the top level. We can ensure
|
||||
the top level with another if statement.
|
||||
|
||||
The *Level* page control allows you to get data from the page's parents, e.g. if you used *Level(1)*, you could use:
|
||||
|
||||
|
||||
:::ss
|
||||
$Level(1).Title
|
||||
|
||||
|
Loading…
x
Reference in New Issue
Block a user