Integrated system that communicates clearly and touches every part of a website’s life-cycle.
We build websites—not “academic websites.”
We’re responsible for a collection of 150+ of them.
Most of my time was spent researching—not coding.
Working code is an accomplishment, but alone sets the bar too low.
Code should have purpose, and the purpose of all code is to solve problems—not be an impediment.
A flat, single-page HTML template, containing our best practices (proprietary).
I wanted to move from one page to a set of pages.
A PHP template seemed appropriate.
If a PHP template made my work easier, wouldn’t it make everyone’s?
Instead of sharing static pages, I’d share a dynamic site-builder.
If it ran on my server, why not on Production?
Using style patterns, their combination make unique designs.
Harness the power of Gamut Core for experimentation and visual design construction.
JS, HTML, CSS are REAL CODE (not fake or sub-standard or easier).
There are great benefits applying the principles and best practices of “real” programming to them.
—John “Hannibal” Smith: The A-team
Variables set at the site level inform central, shared SASS so each site can have its own values for breakpoints/values but share CSS.
Shared CSS for modules (search, footer), normalize.css, responsive images, etc. All sites get updates, when they occur, on-the-fly.