In this one hour tutorial Simon Collison will demonstrate why convention, order and understanding are vital to web design and development teams. He'll give insights into how Erskine approach projects and will help attendees explore ways of creating and evolving their own "Ultimate Package".
Why conventions are essential for successful web projects. How Erskine approach HTML, CSS & JavaScript in their own projects. What to consider when developing your own "Ultimate Package".
5. A base layer of rules and
conventions that act as starting
points for HTML, CSS, JavaScript
and ExpressionEngine for
all projects.
6. • Basic HTML files & naming conventions
• PHP for basic templates prior to CMS integration.
• CSS: Stylesheets, IE-specific, reset, scratch files etc.
• JavaScript: jQuery, onload triggers, transparency support
• Other Assets such as folders for images, Flash etc.
7. A bumper compendium of
cascading CSS files, naming
conventions, modules, plugins and
scripts that ensure any project will
stay on convention, and be simple
for anyone to step into and work
with at any time.
8. • Allows better collaboration within the team; the designer
can jump into the developer’s code and vice-versa.
• Anyone who hasn’t even worked on a certain project can
jump in and quickly solve problems because everything is
on convention.
• Keeps output fresh and ensures use of best practices.
• Establishes a thoroughly connected layer of base files
allowing for swift CSS and JavaScript implementation
and other assets.
• Makes life easier for developers and designers... and
anyone really
• Helps maintain quality control
10. We’re constantly considering
HTML, CSS, browsers, JavaScript,
naming conventions, CMS usage
and any improvements in general
methods or implementations.
Constant iterations of the
package are made.
12. We’re currently on version 2.2 - and it’s
available internally on our systems
with a changelog, meaning anyone can
use it as a starting point for both
agency and personal projects.