<?xml version="1.0" encoding="utf-8" ?>
    <website-name>Symphony CMS</website-name>
    <category />
      <item handle="hidden">hidden</item>
      <item handle="index">index</item>
      <item handle="3">3</item>
      <item handle="3">3</item>
    <login-info logged-in="true" id="1" user-type="developer" primary-account="yes">
      <name>John Smith</name>
      <default-area type="page">/blueprints/sections/</default-area>
    <section id="1" handle="articles">Articles</section>
    <entry id="3" comments="0" images="0">
      <title handle="a-primer-to-symphony-2s-default-theme">A primer to Symphony 2's default theme</title>
      <body mode="formatted"><p>Every theme in Symphony has an important mission: to introduce newcomers to Symphony by way of a working example. <em>Spectrum</em>, the name of this version's default theme, was designed and developed with such a mission in mind by following a set of constraints. A default theme is required to:</p><ol><li>be presented in a format that is universally identified and intuitive.</li><li>have a clear and simple HTML structure.</li><li>demonstrate the fundamental concepts in Symphony—<a href="http://symphony-cms.com/learn/concepts/view/sections/">sections</a>, <a href="http://symphony-cms.com/learn/concepts/view/fields/">fields</a>, <a href="http://symphony-cms.com/learn/concepts/view/data-sources/">data sources</a> and <a href="http://symphony-cms.com/learn/concepts/view/events/">events</a>—and their interactions together.</li><li>avoid functionality that does not have any educational value.</li></ol><h4>The design</h4><p>Our first rule states that a default theme needs to be in a format that is instantly recognisable to a user. As a result, all of the themes created in Symphony's history have emphasised a weblog structure. <em>Spectrum</em> continues this tradition.</p><p><em>Cubic</em>, the name of a previous default theme, followed the teaching mandate very closely. However, the theme took it one step further and removed complex structure and colour in favour of a simplified look and feel. The main design goal for <em>Spectrum</em> is to introduce more colours but still follow the philosophy of a simplistic layout.</p><h4>Features</h4><p><em>Spectrum</em> has a handful of additional features that you won't find in previous default themes. These new features are not only meant to demonstrate the capabilities of the system but also explain some fundamental philosophies in Symphony 2. Below is a list of features:</p><ul><li>Logged in users will see links to Symphony's admin to edit articles, manage comments and add notes.</li><li>Logged in users will see 3 protected menu items, article drafts, the debug page and a link to the Symphony admin.</li><li>Articles on the drafts page sport a button to publish the article.</li><li>Article images take advantage of Symphony's built-in image manipulation feature to crop and size the image automatically.</li><li>The contact form on the about page saves the content to the Messages section on the back end and emails the website's owner.</li></ul><h4>Philosophy</h4><p>All of the above takes advantage of new features found in version 2. An important concept that is being advocated in Symphony is the practise of creating a tighter connection between the front end and the back end. Developers are encouraged to take advantage of the simplified URL structure of the admin to create a more convenient environment for their users.</p><p>With the introduction of the Event editor, developers now have even more control when developing a website. For example, the <em>Publish</em> button on the <a href="/drafts/">article drafts page</a> utilises the event editor to create an interaction between the front end and the back end. This allows the <em>Publish</em> button to update the "Publish this article" checkbox field from the "Articles" section. This feature also complements and encourages the philosophy of a more seamless environment between the website and the admin interface.</p>
      <date iso="2011-01-02T18:34:00-08:00" time="18:34" weekday="7" offset="-0800">2011-01-02</date>
        <item id="1" handle="symphony" section-handle="categories" section-name="Categories">Symphony</item>
    <page handle="home" id="64">
    <page handle="articles" id="69">
    <page handle="drafts" id="70">
    <page handle="archive" id="68">
    <page handle="about" id="66">
    <page handle="rss" id="67">
    <page handle="maintenance" id="75">
    <page handle="page-not-found" id="76">
      <name>Page Not Found</name>
    <section id="3" handle="notes">Notes</section>
    <entry id="6">
      <date iso="2011-02-22T20:55:00-08:00" time="20:55" weekday="2" offset="-0800">2011-02-22</date>
      <note mode="formatted"><p>Follow the Symphony team (<a href="http://twitter.com/symphonycms">@symphonycms</a>) and the Symphony community (<a href="http://twitter.com/search?q=%23symphonycms">#symphonycms</a>) on Twitter.</p>
    <entry id="5">
      <date iso="2011-02-22T20:54:00-08:00" time="20:54" weekday="2" offset="-0800">2011-02-22</date>
      <note mode="formatted"><p>Check the official <a href="http://symphony-cms.com/downloads/">Symphony downloads page</a> for a full list of extensions, ensembles and XSLT utilities.</p>
    <section id="5" handle="images">Images</section>
    <error>No records found.</error>
Plain XML