designermonkey

• Draft Number: 1
• Date: 2013-04-14
• Author: John Porter @designermonkey

Symphony Next

This is all still a little new to me, so forgive me if this sounds naive, or you all have already thought about this and it's obvious, but I've been thinking about how we actually build Next. (I like this as a project codename).

Proposing the Application

designermonkey

Symphony CMS

Event System Updates

Here are some ideas to upgrade the events system in Symphony.

Event Codes

Error codes, following a similar syntax to HTTP Errors, would allow some great control of what will be displayed to the user upon success or failure of the event. These base error codes should be provided by the base Event class as constants, providing

designermonkey

<?xml version="1.0" encoding="UTF-8"?>
<data>
    <site-basket-contents>
        <group id="basket">
            <item id="261" count="1">
                <item id="price">135.00</item>
                <item id="shipping">9.50</item>
            </item>
            <item id="57" count="1">
                <item id="price">58.50</item>

designermonkey

<?xml version="1.0" encoding="UTF-8"?>
<data>
    <products>
        <entry id="1">
            <name>Test</name>
            <public-price>10.00</public-price>
            <trade-price>8.00</trade-price>
        </entry>
        <entry id="2">
            <name>Test</name>

designermonkey

<data>
  <store-product-offers>
    <section id="14" handle="special-offers">Special Offers</section>
    <entry id="127">
      <product>
        <item id="68" handle="br1-a-line-petticoat" section-handle="products" section-name="Products">BR1 (A-line petticoat)</item>
      </product>
      <country>
        <item id="14" handle="united-states" section-handle="countries" section-name="Countries">United States</item>
      </country>

designermonkey

<data>
  <products>
    <entry>one</entry>
    <entry>two</entry>
    <entry>three</entry>
    <entry>four</entry>
    <entry>five</entry>
    <entry>six</entry>
    <entry>seven</entry>
    <entry>eight</entry>

designermonkey

<data>
    <datasource>
        <section handle="test-section">Test Section</section>
        <entry>
            <page-path handle="about">/about</page-path>
            <page-title handle="about">About</page-title>
            <title handle="about-this-company">About This Company</title>
            <template>
                <item id="2" handle="content" section-handle="page-templates" section-name="Page Templates">Content</item>
            </template>

designermonkey

<data>
    <thumbs>
        <item>120</item>
        <item>240</item>
        <item>360</item>
    </thumbs>
</data>

designermonkey

<data>
    <aspectratios>
        <item name="onebyone">1</item>
        <item name="onebytwo">0.5</item>
        <item name="onebythree">0.33333</item>
        <item name="twobyone">2</item>
        <item name="twobythree">0.66667</item>
        <item name="twobyfive">0.4</item>
        <item name="threebyone">3</item>
        <item name="threebytwo">1.5</item>

designermonkey

#Recommendations

A list of recommendations for the office and workflow.

1. Repositories and Tracking.

   • Bitbucket - 100% free git repository hosting. Quality issue tracking like Github, only completely free.
   • BitbucketCards - Kanban Agile issue management for Bitbucket repos. Teh awesomes. Teh blog post.

2. Workflow

   • Github Flow is used by Github and is a very uick and easy "community" based workflow.