| body { | |
| -webkit-font-smoothing: antialiased; | |
| -moz-font-smoothing: antialiased; | |
| -ms-font-smoothing: antialiased; | |
| font-smoothing: antialiased; | |
| -moz-text-shadow: 0 0 1px rgba(0, 0, 0, 0.01); | |
| -ms-text-shadow: 0 0 1px rgba(0, 0, 0, 0.01); | |
| text-shadow: 0 0 1px rgba(0, 0, 0, 0.01); | |
Attention: the list was moved to https://github.com/vitorbritto/dev-list
This page is not maintained anymore, please update your bookmarks.
Recently, I decided to organize my bookmarks. So, like a good fellow, I am sharing with you. I hope you enjoy!
#Recommendations
A list of recommendations for the office and workflow.
Repositories and Tracking.
Workflow
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 (input), the website will take 'action' and do something with the data (processing) and then provide a user with the result (output). Symphony provides this logic layer via events.
This tutorial is about customising Symphony events. You will learn about:
load and __trigger)$_POST array
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.