2 web designers
2 web developers
1 CMS trainer
Not in the group but key
Digital Imaging Coordinator
Liaison with Computing and Computer Information Services (CIS)
A flat, single-page HTML template, containing our best practices (developed in-house).
I used a PHP template to replicate the sample page across a site.
If a PHP template made my work easier, wouldn’t it make everyone’s?
Instead of sharing a static page, share a dynamic site-builder.
If it ran on my server, why not on Production?
A system for maintaining the website lifecycle for multiple sites.
Decide there is only one website.
One website with 150+ variants.
Determine what makes a website a website,
vs. what makes a website a unique website.
As applied to components:
Centralize components shared by 2+ sites.
Components existing on only one site, remain there.
Complex code is embarrassing.
Not technically incorrect and program “works,” but:
Slows down development
Increases risk of bugs or failures
Don’t only apply to computer science.
Much of my time was spent researching—not coding.
Code that “works” isn’t sufficient.
Have purpose and solve problems.
Gamut isn’t a CMS.
It allows a CMS to focus on content management.
Just because it can…doesn’t mean it should.
Does it adhere to web standards?
Follow web BPs?
Allow you to use the tools you want?
Off-the-shelf ≠ exactly what we need.
Gamut is designed to work with other CMSs or none at all.
There is no particular “type” of site we are building.
There is only one website.
One site with many variants.
Centralization ≠ cookie cutter
But using variables with SASS can avoid overrides.
Variables are set locally but affect central SASS
We’re compiling SASS on-the-fly with PHP using Leaf Corcoran’s SASSPHP (w/caching)
Meaning, each site can have its own values, but still share CSS.
Using style patterns, their combination make unique designs.
Harness the power of Gamut Core for experimentation and visual design construction.