| <?php if ( ! defined('BASEPATH')) exit('No direct script access allowed'); | |
| // Simple, single configuration file to override almost all paths and server settings. As used by @airways | |
| // and @litzinger. | |
| // Only check in the default as dist.config.php, set your version control system to ignore config.php so that | |
| // local users and each instance (staging, production) can have their own settings. | |
| // These config files are mainly meant to be used on a shared development server used by all developers, | |
| // although it works almost as well for local development as well. |
For this tutorial I'm assuming you are already comfortable with CSS, Sass (I'll use the SCSS syntax) and Compass. Please get set up with each one of those before attempting to use Susy. Sass and Compass both have their own setup instructions and tutorials that you can use.
There is also reference documentation in the works.
CSS Systems
| <xsl:call-template name="pagination"> | |
| <xsl:with-param name="pagination" select="pagination" /> | |
| <!-- build an url that holds every get params, except the page --> | |
| <xsl:with-param name="pagination-url"> | |
| <xsl:value-of select="/data/params/root" /> | |
| <xsl:value-of select="/data/params/parent-path" /> | |
| <xsl:text>?</xsl:text> | |
| <xsl:for-each select="/data/params/*[contains(name(), 'url-')]"> | |
| <xsl:if test="not(name(.) = 'url-page')"> | |
| <xsl:value-of select="concat(substring-after(name(), 'url-'), '=', text())" /> |
| @mixin ie6 { * html & { @content } } | |
| #logo { | |
| background-image: url("/images/logo.png"); | |
| @include ie6 { background-image: url("/images/logo.gif"); } | |
| } |
See the official Susy site for 1.0 documentation.
| [ | |
| { "keys": ["ctrl+shift+x"], "command": "tidy_xml" }, | |
| { "keys": ["ctrl+shift+j"], "command": "prettify_json" } | |
| ] |
| <!DOCTYPE html> | |
| <html> | |
| <head> | |
| <meta charset="utf-8"> | |
| <title>example crossroads + hasher</title> | |
| <meta name="viewport" content="width=device-width, initial-scale=1.0"> | |
| </head> | |
| <body> | |
| <div id="wrapper"> | |
| <ul> |
Forms have been an integral part of any interactive site since the dawn of time, they promote interactivity and are usually the most common way users interact with a site. It's commonplace that when a form is submitted, the website will take 'action' and do something with the data and then provide a user with the result. Symphony provides this logic layer via Events.
This tutorial assumes you have a basic understanding of how Events work in Symphony (if not, this may be a good introduction) and are semi comfortable writing some PHP code. I'll be showing you some of the lesser known features of Symphony Events, including event priority, event chaining and a brief demonstration of how to write a custom Event. The difficulty level progresses as we go through, but with any luck you'll be able to learn a thing or two :)
Our client requires a form that allows a user to submit some details about their new car purchase. Th
I'm describing my workflow in these articles, before I start my next Symphony project. Mostly for myself, to iron out my recurring problems, it is based on solid git techniques, taking heed of advice learned from Symphony community members, many many tips on the web, and flicking through the pages of O'Reilly's Version Control with git.
The core aim of this article, is to get a good Symphony development and deployment environment using git as the basis for the organisation, and have it written down for reference.
This workflow can be applied to any project, in theory, that has a starting point being a private remote git repo.