Jayme Cochrane dot com http://jaymecochrane.com Jayme Cochrane dot com Feed en-us Symphony (build 2000) A primer to Symphony 2's default theme http://jaymecochrane.com/entries/a-primer-to-symphony-2s-default-theme/ Sat, 26 Jan 2008 12:25 +0100 http://jaymecochrane.com/articles/a-primer-to-symphony-2s-default-theme/ <p>Every theme in Symphony has am important mission: to introduce newcomers to Symphony by way of a working example. <em>Spectrum</em>, the name of this version&#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:</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 - <code>sections</code>, <code>fields</code>, <code>data sources</code> and <code>events</code> 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&#8217;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&#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:</p> <ul> <li>Logged in users will see Links to Symphony&#8217;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>Website authors who have access to the admin can make their comments &#8220;authorised&#8221; which will colour their comment different to others.</li> <li>Articles on the drafts page sports a button to publish the article.</li> <li>Article images take advantage of Symphony&#8217;s build-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 backend and emails the website&#8217;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 backend. 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 frontend and the backend. This allows the <em>Publish</em> button to update the &#8220;Publish this article&#8221; checkbox field from the &#8220;Articles&#8221; section. This feature also compliments and encourages the philosophy of a more seamless environment between the website and the admin interface.</p>