<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0">
  <channel>
    <title>NOTEXCEPTIONAL</title>
    <link>http://notexceptional.com</link>
    <description>NOTEXCEPTIONAL Feed</description>
    <language>en-us</language>
    <generator>Symphony (build 2000)</generator>
    <atom:link href="http://notexceptional.com/rss/" rel="self" type="application/rss+xml"/>
    <item>
      <title>A primer to Symphony 2's default theme</title>
      <link>http://notexceptional.com/entries/a-primer-to-symphony-2s-default-theme/</link>
      <pubDate>Mon, 08 Dec 2008 11:00 +1100</pubDate>
      <guid>http://notexceptional.com/articles/a-primer-to-symphony-2s-default-theme/</guid>
      <description>&lt;p&gt;Every theme in Symphony has am important mission: to introduce newcomers to Symphony by way of a working example. &lt;em&gt;Spectrum&lt;/em&gt;, the name of this version&amp;#8217;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:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;be presented in a format that is universally identified and intuitive.&lt;/li&gt;
&lt;li&gt;have a clear and simple HTML structure.&lt;/li&gt;
&lt;li&gt;demonstrate the fundamental concepts in Symphony - &lt;code&gt;sections&lt;/code&gt;, &lt;code&gt;fields&lt;/code&gt;, &lt;code&gt;data sources&lt;/code&gt; and &lt;code&gt;events&lt;/code&gt; and their interactions together.&lt;/li&gt;
&lt;li&gt;avoid functionality that does not have any educational value.&lt;/li&gt;
&lt;/ol&gt;

&lt;h4&gt;The design&lt;/h4&gt;

&lt;p&gt;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&amp;#8217;s history have emphasised a weblog structure. &lt;em&gt;Spectrum&lt;/em&gt; continues this tradition.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Cubic&lt;/em&gt;, 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 &lt;em&gt;Spectrum&lt;/em&gt; is to introduce more colours but still follow the philosophy of a simplistic layout.&lt;/p&gt;

&lt;h4&gt;Features&lt;/h4&gt;

&lt;p&gt;&lt;em&gt;Spectrum&lt;/em&gt; has a handful of additional features that you won&amp;#8217;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:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Logged in users will see Links to Symphony&amp;#8217;s admin to edit articles, manage comments and add notes.&lt;/li&gt;
&lt;li&gt;Logged in users will see 3 protected menu items, article drafts, the debug page and a link to the Symphony admin.&lt;/li&gt;
&lt;li&gt;Website authors who have access to the admin can make their comments &amp;#8220;authorised&amp;#8221; which will colour their comment different to others.&lt;/li&gt;
&lt;li&gt;Articles on the drafts page sports a button to publish the article.&lt;/li&gt;
&lt;li&gt;Article images take advantage of Symphony&amp;#8217;s build-in image manipulation feature to crop and size the image automatically.&lt;/li&gt;
&lt;li&gt;The contact form on the about page saves the content to the Messages section on the backend and emails the website&amp;#8217;s owner.&lt;/li&gt;
&lt;/ul&gt;

&lt;h4&gt;Philosophy&lt;/h4&gt;

&lt;p&gt;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 backend. Developers are encouraged to take advantage of the simplified URL structure of the admin to create a more convenient environment for their users.&lt;/p&gt;

&lt;p&gt;With the introduction of the Event editor, developers now have even more control when developing a website. For example, the &lt;em&gt;Publish&lt;/em&gt; button on the &lt;a href="drafts/"&gt;article drafts page&lt;/a&gt; utilises the event editor to create an interaction between the frontend and the backend. This allows the &lt;em&gt;Publish&lt;/em&gt; button to update the &amp;#8220;Publish this article&amp;#8221; checkbox field from the &amp;#8220;Articles&amp;#8221; section. This feature also compliments and encourages the philosophy of a more seamless environment between the website and the admin interface.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
