developing a site that does not rely on you.
You being the key word.
process for multi-person development teams.
keeping the team healthy.
streamlining your business processes.
It is not...
CSS built before data architecture plan or development
CSS built before content types
CSS built before Views
CSS built before proliferated content
CSS built before ﬁddling with the TPLs
About writing HTML
Limited to theming
It’s about relying on
The markup structure that is coming from the
Using the markup provided by modules like
Views and CCK.
And if you have a problem with the markup,
get involved in making it better, in core, and
not rewriting it yourself.
It may not be for...
a solo web developer
a person who will never update a site.
unless we can get him drunk enough
Avoid having to start from scratch every time.
Easier to work in parallel with other teams.
So the client/maintainer can extend the
site...without you, or a developer, or CSS
additions, or HTML modiﬁcations, or TPL
Why can’t we...
put the power in the hands of the user?
make ourselves replaceable?
make things easier on the maintainer?
There is no stylistic approach to HTML or CSS
Re-arranging markup ﬁrst, rarely removing or
Admin before TPL
Consider ease of workﬂow over ease of
Why we use Zen
Because we have Layout method for
commit access markup source
CSS broken out by task
Semantic markup point
Paint by numbers CSS Flexible and complex
Logic based CSS markup and CSS
Why we transitioned
So we could support sites 6+ months after release.
So our clients could extend their own sites.
So our clients could adopt their sites as their own.
So we could have multiple themers on a project.
So we could streamline our process.