Theme Settings - Revision history

Admin: /* File Upload Definitions */

2011-06-16T04:38:14Z

File Upload Definitions

2011-06-14T22:35:59Z

Colour Filters

2011-05-24T03:02:33Z

2011-05-17T00:08:42Z

Enhanced CSS Stylesheet syntax

2011-05-17T00:08:25Z

2011-03-28T23:21:35Z

2011-03-28T23:21:12Z

Syntax

2011-03-28T23:20:40Z

2011-02-01T00:28:43Z

2011-02-01T00:23:18Z

@@ Line 374: / Line 374: @@
    max_width: 900
+}
 </pre>

@@ Line 623: / Line 623: @@
 * adjust_hue: percent (Positive or Negative)
 * adjust_saturation: percent (Positive or Negative)
 For example, the following produces a highlight from a given base colour.
@@ Line 637: / Line 638: @@
 The Colour Filters may also be chained together to product complex colour effects.
 More details on Liquid Filters can be found in the Liquid [[Liquid Basics#Filter Reference|Filter Reference]]

@@ Line 543: / Line 543: @@
 <pre>
    {{ linklists[settings.home_menu].menu }}
 </pre>

@@ Line 39: / Line 39: @@
 Default values can be defined in the settings file and these values are used when the user has not saved their own preferences.
-=== Enhanced CSS Stylesheet syntax ===
+=== Enhanced CSS stylesheet syntax ===
 Whenever you use a <code>.css.liquid</code> file extension, the stylesheet is parsed for Liquid tags as mentioned above. This enables you to include standard Liquid tags to add conditional logic and variable substitution into the stylesheet.
@@ Line 47: / Line 47: @@
 '''SCSS''' offers many benefits and allows you to simplify complex stylesheets by using variables, nested attributes and mixins.
 As an additional benefit, even if you are using only standard '''CSS''' syntax, the resulting <code>.css</code> file is compressed so that the file size is reduced to a minimum. This will help your template files to load faster and will result in a better customer experience.
 == The theme.settings file ==

← Older revision		Revision as of 00:08, 17 May 2011
Line 38:		Line 38:

	Default values can be defined in the settings file and these values are used when the user has not saved their own preferences.		Default values can be defined in the settings file and these values are used when the user has not saved their own preferences.
		+
		+	=== Enhanced CSS Stylesheet syntax ===
		+
		+	Whenever you use a <code>.css.liquid</code> file extension, the stylesheet is parsed for Liquid tags as mentioned above. This enables you to include standard Liquid tags to add conditional logic and variable substitution into the stylesheet.
		+
		+	In addition, each stylesheet is then parsed using '''SCSS''' syntax that supports extensions to the CSS3 standard. Further information on the '''SCSS''' extensions can be found at http://sass-lang.com/
		+
		+	'''SCSS''' offers many benefits and allows you to simplify complex stylesheets by using variables, nested attributes and mixins.
		+
		+	As an additional benefit, even if you are using only standard '''CSS''' syntax, the resulting <code>.css</code> file is compressed so that the file size is reduced to a minimum. This will help your template files to load faster and will result in a better customer experience.

	== The theme.settings file ==		== The theme.settings file ==

@@ Line 17: / Line 17: @@
 * Additionally, any files with a suffix of <code>.liquid</code> residing in the <code>assets</code> directory will be processed for Liquid tags, and the corresponding file without the <code>.liquid</code> suffix will be generated. This can be ued to generate CSS and JavaScript files from Liquid templates.
-The form rendered at the top of the Theme Editor page contains a number of input fields an controls that are defined in the <code>layout.settings</code> file.
+The form rendered at the top of the Theme Editor page contains a number of input fields an controls that are defined in the <code>theme.settings</code> file.
 Each field in the settings file is mapped to a <code>settings</code> object attribute.

@@ Line 43: / Line 43: @@
 === Syntax ===
-The <code>layout.settings</code> file contains all the definitions for your theme settings.
+The <code>theme.settings</code> file contains all the definitions for your theme settings.
 The file contains comments, parts, sections and definitions. You can use spaces to format the file, but they are not significant, except within strings.
-This is a sample <code>layout.settings</code> file:
+This is a sample <code>theme.settings</code> file:
 <pre>

@@ Line 7: / Line 7: @@
 The current support for themes has now been enhanced to enable a theme settings configuration file to be added to any theme which will provide simple customization options for the end-user.
-Theme Settings are enabled when a theme contains the file <code>layout.settings</code> in the <code>layout</code> directory.
+Theme Settings are enabled when a theme contains the file <code>theme.settings</code> in the <code>layout</code> directory.
 When Theme Settings are enabled, the following actions will occur:
-* The <code>layout.settings</code> file will be parsed for all the settings definitions.
+* The <code>theme.settings</code> file will be parsed for all the settings definitions.
 * A form will be built from these definitions and will be displayed as part of the 'Theme Editor' page.
 * The user can choose the settings that are appropriate for their needs and save them.
@@ Line 39: / Line 39: @@
 Default values can be defined in the settings file and these values are used when the user has not saved their own preferences.
-== The layout.settings file ==
+== The theme.settings file ==
 === Syntax ===

@@ Line 521: / Line 521: @@
    ...
    {% endfor %}
 </pre>

@@ Line 502: / Line 502: @@
 ==== menu ====
-The <code>page</code> class may be used in <code>select</code> or <code>radio</code> field definitions to populate the field with a list of the store's published pages.
+The <code>menu</code> class may be used in <code>select</code> or <code>radio</code> field definitions to populate the field with a list of the store's menus.
 If this class is specified, no <code>options</code> attribute is required.
 <pre>
-home_page: {
+home_menu: {
-   label: "Choose the page to be displayed on the Home page",
+   label: "Choose the menu to be displayed on the Home page",
    type: select,
-   class: page,
+   class: menu,
-   selected: home
+   selected: main-menu
+}
 </pre>
-The <code>page</code> class works similarly to the <code>collection</code> class.
+The <code>menu</code> class works similarly to the <code>collection</code> class.
 <pre>
-   {{ pages[settings.home_page].content }}
+   {% for link in linklists[settings.home_menu].links %}
 </pre>