Closed Bug 1438585 Opened 8 years ago Closed 8 years ago

Set up/automate build process for Mozilla design system site

Categories

(www.mozilla.org :: Pages & Content, enhancement)

Production
enhancement
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: craigcook, Unassigned)

Details

We're making a design system! It will live on the web and the site is based on a Node static site generator called Drizzle (which is itself based on one called Fabricator). Templates are built in handlebars and/or markdown then converted into HTML for distribution. We need to do a bit of work to automate the build process and deploy to a server, likely via circleci or something like that, and this is where I hit the end of my skillset. We also need to decide on a home for this. It could be hosted on github pages or AWS (in which case we'll also need a domain or subdomain). For the moment the repo I'm working in is https://github.com/craigcook/design-system and I've been building locally (with gulp) and manually deploying to github pages https://craigcook.github.io/design-system/. As part of this we should also move the repo to an official home in the Mozilla org and make sure the appropriate group of folks have access.
Craig - can you update status on this please?
Flags: needinfo?(craigcook.bugz)
pmac set us up with Netlify and an automatic build triggered whenever a commit is added to master. For now the site lives at https://moz-web-design-system.netlify.com/ but we can eventually map that to a proper domain (pending a proper name).
Status: NEW → RESOLVED
Closed: 8 years ago
Flags: needinfo?(craigcook.bugz)
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.