Symphony – Ensembles

Pears

Sun, 07 Oct 2012 17:00:00 +1000

A markup & style pattern library

By bauhouse

Dan Cedarholm announced Pears on 6 February 2012.

Yesterday, on stage at An Event Apart Atlanta, I announced Pears: an open source WordPress theme for creating your own markup & style pattern library.

I wanted to create my own database repository of commonly used patterns and figured the tool might be useful for others as well. Breaking interfaces down into patterns has been immensely helpful in learning and re-evaluating the best possible code to implement them. I’ve just gotten started and will be adding more as I create them.

But Pears isn’t about how I code these patterns—it’s a tool for creating your own.

The theme is available on GitHub for those that want to chip in and make it even better. Admittedly, the code is a little rough here and there, but it works.

Looking forward to seeing others’ takes on the patterns that power flexible web interfaces.

When I saw the Pears theme that Dan Cedarholm had created for WordPress, I thought it would make a great Symphony ensemble. So, I created this Symphony ensemble. I chose to start from scratch, rather than fork the WordPress theme, so as not to bloat this repository.

A Symphony ensemble is a means of packaging a site as an installer, used by the Symphony development team to package the official releases. It also works well as a way to share entire sites without worrying about sharing sensitive author login details and database credentials.

This ensemble demonstrates my usual process of building an ensemble with the Symphony core as the master branch and the workspace directory as the workspace branch. I use the Export Ensemble and the Dump DB extensions to track database changes in the Git repository, so it is possible to revert back to a previous version and restore the database to the state it was in at the time of that commit.

Installing this Symphony Ensemble

Follow the usual instructions for installing Symphony. You'll find these instructions in the README file of the master branch. More detailed install instructions can be found on the Symphony site.

If you are installing with Git, the difference will be that you don't need to clone the Symphony core files. These files are in the master branch of this repository, which is a snapshot of the Symphony core, slightly modified to accommodate references to the extension submodules that have been added to the core extensions, and the workspace submodule, which contains the majority of the project-specific code that makes this ensemble work. The easiest way to grab everything is to use this single command, which will recursively find all submodules, initialize them and checkout the appropriate commit, cloning the files into a directory called pears:

git clone --recursive git://github.com/bauhouse/sym-pears.git pears

Alternatively, just download the ZIP file of the latest release and install the old fashioned way.

Change Log

Version 1.1 - 8 October 2012

Updated the Pears ensemble to Symphony 2.3

Version 1.0 - 7 October 2012

Ported the Pears project to Symphony 2.2.5

Enjoy Two Different Flavours of Pears

Now you have your choice of CMS on which to build your pattern library: WordPress or Symphony. You can find more about the original WordPress theme below.

A WordPress Theme by Dan Cedarholm

Pears are common patterns of markup & style.

Pears is an open source WordPress theme. I'll admit the code is a bit rough, initially based on the default 'twentyone' theme.

I wanted a handy way of collecting HTML & CSS pattern pairs. Often used modules with a minimal of style applied. It's become a valuable learning tool, whereby breaking interfaces down into small pieces make it easier to learn and improve running code.

HOW TO ADD CODE PATTERNS

Each pattern is a post in WordPress.
Add markup in a custom field named 'html'.
Add style in a custom field named 'css'.
Use the main content field for optional notes.

Learn more and see it in action here: http://pea.rs

Enjoy.

Dan Cederholm Salem, Massachusetts February, 2012 http://simplebits.com

DesignProjectX

Thu, 04 Oct 2012 17:00:00 +1000

Symphony Tutorials

By bauhouse

A site about learning by doing

This site takes you through the process of building a Symphony site, from Hello, world to Ninja Domains: A Multi-Domain Setup using the Symphony XSLT Content Management System.

View the Symphony CMS Tutorials and follow the process step by step. View the XML, XSL and text files that have been used to put the site together. While the content is a few years old, the basic philosophies, concepts and processes behind Symphony have not changed much.

Change Log

Version 0.4 Updated for Symphony 2.3
Version 0.3 Updated for Symphony 2.2.x
Version 0.2 Updated for Symphony 2.0.6
Version 0.1 Updated for Symphony 2.0.4

Symphtml5

Sat, 31 Dec 2011 17:00:00 +1000

HTML5 starter ensemble, based on the Fiverstarter boilerplate

By XBleed

Hey guys, I figured I would share my html5 base / starter ensemble. It isn't much, as it serves a purpose similar to the popular html5 boilerplate, but it should be a good kick start for your html5 projects.

As of version 0.4, this is now set up to use the same idea behind my own personal boilerplate, Fiverstarter. This means it now utilizes normalize, headjs, humans.txt, and my responsive grid (which is a modified version of the 1140px grid by Andy Taylor).

Special thanks to @nickdunn, @michael-e, @bauhouse, and anyone else who may have contributed to the HTML5 Doctype extension.

Changelog

0.5 - December 31st, 2011

Updated to Symphony 2.2.5
Removed scripts.xsl utility, replaced with xsl:template modes
Updated jquery to 1.7.1

0.4 - August 23rd, 2011

Updated to Symphony 2.2.3
Removed reset.css for normalize.css
Cleaned up some left unnecessary leftovers from previous versions
Added scripts.xsl back in (not sure how that went away)
Added in a responsive grid system

0.3 - August 3rd, 2011

Updated to Symphony 2.2.2
Updated jquery to 1.6.2
Removed formalize (It's nice, I just never ended up using it)

0.2.1 - May 23rd, 2011

Changed the readme to reflect this specific ensemble
Updated jquery to 1.6.1

0.2 - April 28th, 2011

Updated to Symphony 2.2.1
Bug fix for incorrect workspace variable in scripts
Moved scripts to a separate utility
Changed jquery to 1.6

0.1 - March 3rd, 2011

Initial commit

Bootstrap

Fri, 14 Oct 2011 17:00:00 +1000

A Responsive Development Toolkit

By bauhouse

Bootstrap is Twitter's toolkit for kickstarting CSS for websites, apps, and more. It includes base CSS styles for typography, forms, buttons, tables, grids, navigation, alerts, and more.

To view the original -- checkout http://twitter.github.com/bootstrap!

For this ensemble, the original has been modified to use the Sections Grid from the Markup Library to enable the markup and styles from the Bootstrap toolkit to be used in responsive web design.

The ensemble demonstrates the possibility of using two sections in Symphony to manage snippets of HTML and dynamically arrange the content of a complex page layout, using a fluid grid system. The layout is based on modifications to Bootstrap, from Twitter to create a responsive version of Bootstrap, as a fork of the original repository on GitHub.

Clone the Git Repository for the Ensemble

The ensemble pulls the responsive branch of the Domain7 fork into the workspace as a submodule. To clone the ensemble repository, use the following command:

git clone --recursive git://github.com/builders/sym-bootstrap.git bootstrap

This will clone version 2.2.3 of the Symphony core and recursively clone all submodules, including extensions and the workspace, to be able to install Symphony with the responsive version of Bootstrap.

Download the Ensemble

Or, if you don't want to use Git, just download the complete ensemble from GitHub as a ZIP archive.

Installing Symphony

For instructions on installing Symphony, refer to the README file in the master branch of this ensemble, which is a fork of the master branch of the Symphony CMS repository, modified to include submodules for additional extensions and the workspace. You can also find guides for installing and using Symphony on the Symphony CMS site.

Just the HTML and CSS

Or, if you just want the HTML and CSS, just clone the responsive branch of the Domain7 fork of the Bootstrap toolkit.

git clone --branch responsive git://github.com/domain7/bootstrap.git

All changes have been added to the css directory, and are demonstrated by the index.html in the responsive directory. A responsive page template example has also been added to the examples directory.

A Work in Progress

The responsive version is still a work in progress and the CSS has not been optimized or minimized. There is still work to be done on the form fields, navigation and other design patterns to optimize them for use in responsive web design.

As always, feel free to fork the repository, make changes and submit a pull request to improve on this first attempt at a responsive version of Bootstrap.

Issues

Please log any issues you find for the responsive version of Bootstrap using the issues tracker on GitHub.

Please log any issues you find for the Symphony Bootstrap Ensemble using the issues tracker on GitHub.

Please log any issues you find for Symphony CMS using the issues tracker on GitHub.

Symphony Demo

Tue, 24 May 2011 09:00:00 +1000

Highly customizable and entry based pagebuilding

By Cremol

Symphony Demo Highly customizable and entry based pagebuilding

This ensemble is the result of a demo-site, that i made to explore some of Symphony's features and it's user friendly back-end.

The design is insprired by symphony's back-end, but fully customizable. You can experiment with body, header, menu and caption colors in the 'preferences' section. Also included a complete reference to the google webfont directory, so you can choose from over a hundred webfonts for website title and captions. Entering your favourite twitter username will display it's tweets on the homepage!

Pages and a recursive navigation can be created through entries in the 'pages' section. Choosing a parent page will create a multilevel menu. (credits) The pages are built out of a single template, with optional sidebar and / or slideshow.

The homepage consists of a blog, showing text, an optional gallery and comments.

Enjoy and show your creativity!

Changelog
0.1 - May 24rd, 2011
0.2 - Oktober 13th, 2011 // Updated to Symphony 2.2.3

Dynamic Flash

Sun, 28 Nov 2010 00:00:00 +1000

Symphony back end for dynamic Flash sites

By silexlabs

Install this ensemble and use Symphony to manage your Flash content.

This ensemble is provided by Silex Labs. It is targeting Flash developers and Silex designers.

Login in Symphony as admin and you can define new structures which will generate forms to be filled by the user in user mode. The user logs in as a user and he can create lists of objects with these structures. For example, we included a structure called "gallery element", so that the user mode lets you create new elements for a galery, with a name, description and a file upload form.

With Silex or Flash, you can do templates or sites which display the data entered by the user. In Silex, no programming skills is needed and in Flash, you will develop in ActionScript needed. Here is a demo of Symphony+Silex: http://demos.silexlabs.org/dynamic_demo/ . And here is the full Silex server + symphony ensemble for installation on your server: http://hoyau.info/transfert/dynamic_demo.zip

In symphony you will be able to - define structures which will be seen by the user as very simple forms, with text fields, color pickers, calendars, upload forms... - generate URLs where Flash or Silex can get XML "files" created by the user

you will - load the XML data and parse it into a structure you like - display the data as a gallery, a menu or use the data as constants and configuration data

In symphony, the users (your clients) can - manage content in Symphony to display it in Flash or Silex - create elements for a list which is defined in Symphony admin mode - upload files, enter description, chose a date in a calendar... - manage the elements - delete, ducplicate, edit, ...

Q&A

What is the difference between a Silex theme and a Silex template?

The theme is a Silex publication - usually a web site, which is filled with dummy content.

What we call a Silex template, or "dynamic theme" is a publication with content coming from an external source.

What is Silex Labs exchange platform?

The exchange platform is accessible at http://exchange.silexlabs.org/ and contains Silex elements to download: themes, plugins, fonts, language files, animation layouts, tools, loaders and dynamic templates. It also contains amfPHP plugins and services, and Oof components - these are other projects of Silex Labs.

It is a WordPress powered platform, which means, a WordPress blog with the "exchange platform" plugin for WordPress installed - http://wordpress.org/extend/plugins/exchange-platform/ . This plugin is open source, developed by Silex Labs and make it easy for anyone to post elements for the different projects. It handles dependencies between plugins, themes, etc. and versions.

For Silex plugins, themes, templates, etc. there is a corresponding plugin, the "exchange platform" plugin for Silex, which let Silex users install elements in one click from within the manager, and be notified there when new versions are available - here is how: http://community.silexlabs.org/silex/help/?p=1447

What is an accessor in Silex?

In Silex, an accessor is a variable accessible to the designers in the visual editing tools. It can be manipulated visually and it is replaced by its value at runtime. This value usually comes form an external source.

For example, I can put this in a text field in Silex:

Your version of Silex is: <<silex.config.version>> On the stage, I will see "Your version of Silex is 1.6.1RC1", but in the text editor, I see the accessor. And also I can format the accessor and the text field, it will be kept when the value will be changed.

Note that an accessor can also take a color as a value, or

What is a Silex+Symphony template?

It is a pair of 1 symphony ensemble + 1 corresponding Silex theme.

The symphony ensemble produces the XML feeds awaited by the Silex theme and it contains with a website made in Symphony to administrate the content in a user friendly interface, a back end specifically made to drive the Silex templates.

The ensemble is packaged as a Silex plugin called "Symphony back end". This means that there is a php file to describe the plugin, and the Symphony ensemble which contains the dummy content and the back end.

How are the templates will be distributed?

Each template can be used out of the box. Once Silex and Symphony are installed, it shows a dummy content in the template. The user can enter the admin site to manage the content, or Silex WYSIWYG to edit the design.

What are the next steps?

Please read the issues and you will understand

Intranet

Mon, 25 Oct 2010 17:00:00 +1000

A workspace for HTML/CSS/JavaScript prototyping

By bauhouse

This ensemble was created as an HTML/CSS prototype for a non-profit organization that had requested a Drupal site. The functionality was not built out in Symphony, but it gave me a chance to explore ways of using Symphony and XSLT to create templates with modular pieces.

No extensions are required and no entries have been created. There are only a couple data sources that have been attached, including a Navigation data source that is used for dynamically building the navigation structure.

The CSS was also built to be modular and stylesheets can be switched from the Theme menu in the upper right of the front end interface.

The grid system is an adaptation of Nicole Sullivan's Object Oriented CSS framework, though I have taken some license with the framework by renaming some classes. As this was built for an intranet, IE was not as much of a consideration.

A demo of the intranet templates can be found here.

Cities

Mon, 25 Oct 2010 17:00:00 +1000

A custom admin area for a travel site

By bauhouse

This site was originally built with Symphony 2 beta revision 5. I was experimenting with using events and front end forms to create a custom admin system to manage entries for a list of city guides that could be filtered by

Continent
Country
Region
City

City guides can be filtered by section:

Introduction
Accommodations
Destinations
Dining
Entertainment
Information
Tours
Travel
History

Also, content is managed through the custom admin interface. Since content is associated with existing pages, it is not possible to create main navigation pages, but it is possible to reorder the pages. All subpages can be created and edited within this interface.

The workspace has now been updated for Symphony 2.1.2.

The demo site can be viewed here.

Cumulus Tag Cloud

Tue, 19 Oct 2010 17:00:00 +1000

Creating XML for Dynamic Flash

By bauhouse

This ensemble is an implementation of Roy Tanck's WP-Cumulus Flash based tag cloud. It is a demonstration of how to use Symphony to output XML to integrate with a dynamic Flash SWF file.

The Color Chooser Field is used to be able to dynamically modify the link and hover colors of the text.

To view a working example of this ensemble can be viewed at http://sym.domain7.com/demo/cumulus/.

Git Installation

The ensemble repository includes a workspace repository and the Color Chooser Field extension as submodules. To install, run the following commands to install all required extensions and the workspace.

git submodule init
git submodule update

Install Symphony as usual.

Bauhouse

Tue, 05 Oct 2010 17:00:00 +1000

A Design Portfolio Blog

By bauhouse

The Bauhouse Ensemble is a blog portfolio ensemble that is based on a design I created a few years ago. I am releasing this design as an ensemble based on the interest expressed in this thread.

The current implementation of the portfolio involves a very manual process of building five different images for each piece because of the way I’ve implemented it. I developed this probably about three or four years ago when I was first starting out with Symphony. So, it was more a test of what Symphony was capable of than the best way to approach managing a portfolio site. I’m open to suggestions on how this should be improved.

I never got around to implementing comments and gravatars, but this could be added, based on the implementation in the Forum Ensemble, similar to the way this site is working.

Note that I have removed photography from the site. I have included screenshots that I made of earlier versions of Symphony, when I first started writing tutorials for Symphony. This information may have some relevance, but just be aware that many things have changed in the years since I first wrote the tutorials, at the time of version 1.5, I believe.

Installation

Note: This is a work in progress

Installing with Git the easy way

Clone the Bauhouse Ensemble repository and rename the directory (if you like):
```
git clone git://github.com/builders/sym-bauhouse-ensemble.git bauhouse
```
Change directory:
```
cd bauhouse
```

Update all submodules, which will include all extensions and the workspace directory:

git submodule update --init

or, if that doesn't work, issue the commands separately:

git submodule init
git submodule update

Install the ensemble as you would normally install Symphony by pointing your web browser at http://yourwebsite.com/install.php and provide details for establishing a database connection and about your server environment.

Installing with Git the long way

Clone a copy of Symphony 2.1.1. into a directory called bauhouse:

git clone git://github.com/symphonycms/symphony-2.git bauhouse

Change directory:
```
cd bauhouse
```
Initialize the submodules for the default extensions:
```
git submodule init
git submodule update
```

Add the required extensions as submodules:

git submodule add git://github.com/carsten/collapse_sectionfields.git extensions/collapse_sectionfields
git submodule add git://github.com/pointybeard/content_type_mappings.git extensions/content_type_mappings
git submodule add git://github.com/czheng/enhancedtaglist.git extensions/enhancedtaglist
git submodule add git://github.com/bauhouse/export_install_file.git extensions/export_install_file
git submodule add git://github.com/carsten/globalparamloader.git extensions/globalparamloader
git submodule add git://github.com/rowan-lewis/globalresourceloader.git extensions/globalresourceloader
git submodule add git://github.com/ahwayakchih/markitup.git extensions/markitup
git submodule add git://github.com/pointybeard/numberfield.git extensions/numberfield
git submodule add git://github.com/nickdunn/order_entries.git extensions/order_entries
git submodule add git://github.com/pointybeard/pagesfield.git extensions/pagesfield
git submodule add git://github.com/nickdunn/publishfiltering.git extensions/publishfiltering
git submodule add git://github.com/rowan-lewis/logsdevkit.git extensions/logsdevkit
git submodule add git://github.com/nickdunn/entity_diagram.git extensions/entity_diagram
git submodule add git://github.com/czheng/referencelink.git extensions/referencelink
git submodule add git://github.com/rowan-lewis/reflectionfield.git extensions/reflectionfield
git submodule add git://github.com/nickdunn/section_schemas.git extensions/section_schemas

Clone the Symphony workspace for Bauhouse to a directory called workspace:

cd ..
git clone git://github.com/builders/sym-bauhouse-workspace.git workspace

Set permissions to allow Symphony to write files to the server:
```
chmod 777 symphony .
chmod -R 777 workspace
```
Be sure to have an empty database ready for Symphony (or use a different table prefix). Navigate to the root of the install and provide your preferences, server configuration details and primary user information and click the “Install” button to install Symphony 2 and the Bauhouse ensemble.
Secure the site by changing permissions for the root and symphony directories.
```
chmod 755 symphony .
```
Enjoy seeing the world in black, white, grey and a touch of red!

Release Notes

Version 0.2

Date: 5 Oct 2010
Update to Symphony 2.1.1

Version 0.1

Date: 22 March 2010
Initial Release
Symphony 2.0.7

DesignAdmin

Sat, 02 Oct 2010 17:00:00 +1000

A design business admin system

By bauhouse

When I was freelancing under the name bauhouse, I had to wear a lot of hats. Finding the right tools to run my site, administrate my business and facilitate communication with my clients was a challenge.

While in search of tools that could simplify the administration of my design business, I found that software would force me to work a certain way, depending on what I was working on. Duplication of data entry was the biggest frustration. For a freelance business, it would be ideal to enter data once and be able to view information in many forms without having to switch from one application to another.

I found that this was not easily feasible … until Symphony came along. Since the introduction of sections and custom fields that could be configured according to the needs of the Symphony developer, specifically section links (a feature that I requested), I have been thinking about how this feature might be used to build a project management system.

I am in the process of building a project management system that uses Symphony to keep track of clients, projects and timesheets. Eventually, I want it to do everything, because I am tired of switching between several applications (desktop and web) that don’t work together and force me to duplicate my efforts. This is a long-term project, but I am trying to solve problems I have had with running my business since I started it 16 years ago. I have never found a system that does what I need, so I am building it myself - necessity being the mother of invention.

It will be a design business administration system built on the Symphony framework that will track clients, projects, timesheets, estimates, invoices, bookkeeping and accounting reports, tax filing, as well as serve as a client login area to allow basecamp style project management, except with the ability to display work in progress according to project phase, with individual entries for each concept, with commenting enabled for each entry. Once an identity system has been developed, it can then be rolled out within the same system, to display an online corporate identity standards manual and provide a means of distributing logo file formats available for download.

Release Notes

Version 0.2

Date: 2 Oct 2010
Update to Symphony 2.1.1
Update Export Forum Ensemble extension

Version 0.1

Date: 6 July 2010
Initial Release
Symphony 2.0.8RC3

To Do List

Tue, 28 Sep 2010 17:00:00 +1000

A Simple Single Page Application

By bauhouse

Description

Version 0.1 was an experimental ensemble to test Symphony 2.0.8 RC1 and the beta version of the Subsection Manager extension. The ensemble has been updated to Symphony 2.1.1 and the Subsection Manager extension has been updated to version 1.0.1.

The user interface is a pared down version of what I’ve designed for Domain7 in order to track projects with our proprietary set of web tools. This is the beginnings of a project to tear down what I’ve built on top of a proprietary Perl codebase and rebuild it as an open source project management tool.

Usage

The Sites and Resources lists are currently hard-coded. I’m hoping to add the ability to add lists of categories and links for these two columns.

The To Do List column contains a form that allows the ability to edit entries created with the Subsection Manager.

Check off items as done and click the Update Lists button to save entries.
Click on the description for each checkbox item to enable editing of the entry. Click the Update Lists button to save the change.
Click on the name of the list to enable editing of all items in the list.
Click on the To Do List column heading to enable editing of items in both lists
A system navigation bar allows quick access to Symphony admin pages, including Debug Dev Kit page, Profile Dev Kit pages, Publish, Blueprints, System and Symphony CMS Site and GitHub links. There is a User Preferences section in the Symphony admin that can be used to change the setting for displaying this system navigation bar.

Release Notes

Version 0.2

Date: 28 September 2010
Updated to Symphony 2.1.1
Updated Subsection Manager Extension to version 1.0.1

Version 0.1

Date: 21 March 2010
Initial Release
Symphony 2.0.8 RC1
Subsection Manager Extension 1.0dev

Builder

Wed, 16 Jun 2010 09:00:00 +1000

Build new Symphony projects with ease.

By alpacaaa

The workspace of this ensemble is available on github (http://github.com/alpacaaa/builder-workspace).

Requirements:

git if you want to clone repositories
curl if you want to download .zip packages from this website

Pompodium

Fri, 11 Jun 2010 09:00:00 +1000

A magazine-style Ensemble

By Johanna

Three years ago, we set out to create a magazine. What started as an idea to create a platform for photos and articles on typography and design, travel and life finally found it’s destination: this is Pompodium, a free ensemble for Symphony.

After months spent thinking, talking, brainstorming, scribbling, designing, pushing pixels, writing code, being overtaken with new ideas and starting all over again for about three times, the nearly finished website sat untouched for one year. Patiently awaiting its future destiny, the mention of a Symphony meet-up in London finally caused an epiphany to release Pompodium as a magazine-style ensemble for this occasion. Hooray!

An update from Symphony 2.0 beta to 2.0.8, a completely overhauled structure, translation from German to English and matching documentation later, everything is freshened up and ready to play. Pompodium is licenced under Creative Commons and can be downloaded on GitHub. So grab your copy and have fun with it!

Johanna & Nils

Forum

Mon, 24 May 2010 17:00:00 +1000

Fully Functional Forum System

By bauhouse

This forum ensemble is built using the foundation of the official Symphony website’s own discussion area.

For this version of the ensemble, I wanted to make sure that the core was easily updated, so I have deprecated the previous version and started over with the repository to include all the original commits to the Symphony CMS core files. The GitHub repository URL is now different. If you would rather checkout the previous code for the forum, using a modified Symphony 2.0.6 core, use this repository or download the ZIP file.

This version contains some modifications to the extensions in order to ensure compatibility with the Symphony 2.0.8 Release Candidate 1 (RC1), and has been updated to version 2.0.8 RC3. While it is built with the official Frontend Membership Extension, I have used the mail() function instead of the SMTP Email Library (I couldn’t figure out how to get it to work) for registration and activation messages.

The ensemble has not been fully tested. If you find any bugs, please put them on this ensemble’s issue tracker.

Bugaroo

Tue, 09 Mar 2010 01:26:00 +1000

Bugtracker

By phoque

Bugaroo is an attempt to write a simple and beautiful bug tracking system in Symphony. This is a work in progress, feel free to help out!

SimpleViewer

Sun, 29 Nov 2009 00:28:00 +1000

Spectrum with Gallery

By Carsten

This is the SimpleViewer image gallery integrated into the default Spectrum theme. Illustrates how to manage your SimpleViewer galleries with Symphony.

Piano Sonata

Sun, 29 Nov 2009 00:11:00 +1000

Minimalist Blog

By Fazal

Piano Sonata is a blog ensemble. It is currently in beta pending input from you, the wider community. The intention is to eventually replace Spectrum as the default Symphony ensemble.

I’m going to take this opportunity to give you some background information on this ensemble, the scope of work and also the future of it.

This ensemble is based upon a competition entry from my friend Rodrigo Galindez which he submitted to Smashing Magazine. It came in third place and has since done the rounds on many CSS gallery sites for it’s clean design and layout. I asked Rodrigo to let me build an ensemble for Symphony and he kindly agreed.

The theme is designed to highlight some of Symphony’s strengths and features. It should be able to work in it’s own right, and also allow developers to hack and play around with it and make it there own.

The ensemble uses some Symphony extensions, but shouldn’t need to rely on a whole raft of them. The XSL should be accessible and allow newbies and experts alike to approach it. The ensemble comes with some extensions installed, however I haven’t used them all (such as static section), and as such will be removed from the final release.

Please download the ensemble, play with it and suggest any improvements, features or fixes you would like to see happen.

My initial thoughts are to add a photos page, to highlight the remote DS aspect and combine this with JIT. The ensemble uses this to some degree with the twitter integration but I think flickr/picasa integration may be something that could prove beneficial.

Spectrum Members

Sat, 28 Nov 2009 23:51:00 +1000

Spectrum with Membership

By bauhouse

The Spectrum Members ensemble includes a modified workspace for Symphony 2.0.6. This ensemble adds to the Spectrum theme provided in the official workspace repository. The main difference here is that there are three additional pages:

Members
Register
Login

This ensemble is a work in progress. The registration and login forms are working. The retrieve password form is there, but untested at this point. If anyone wants to help out with this, please test this out. Thanks.

Old Popular Yolk

Sat, 28 Nov 2009 13:00:00 +1000

Minimalist Blog

By rainerborene

Old Popular Yolk is a blog ensemble with a clean design. It was originally a theme created by joshuagoodwin and then ported to Symphony by me.