Skip to content

Branding and style guidelines for MIT Technology Review partner and subsidiary sites

Notifications You must be signed in to change notification settings

technologyreview/style-guide

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

MIT Technology Review Web Style Guide

Guidelines to help you align a microsite, partner website, or other affiliate content served to an audience under the MIT brand.

Content

Content templates are located under /public/views/, the Elements template uses /public/views/index.twig.

Requirements

  1. Home Brew (Mac): ruby -e "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/install)" then brew doctor
  2. Node.js: brew install node or by downloading an installing from Nodejs.com
  3. Bower for client-side package management: npm install -g bower

Installation (Mac)

  1. Open up the command line and change to a directory where you want to install the app: cd ~/Sites
  2. Clone the repo to your machine: git clone [email protected]:technologyreview/style-guide.git; cd style-guide
  3. Install Gulp: npm install -g gulp
  4. Run the gulp command to build the project. This will install package dependencies using npm and bowers, and then start the local server
  5. Open the browser to http://localhost:9999

Deployment

The production version of this style guide is hosted at Heroku and has two environments that can be deployed to using Git, staging and production.

To configure easy command-line deployment:

  1. cd to the repo directory on your machine: ~/Sites/mittr-styleguide
  2. Download and install the Heroku Toolbelt
  3. Login to Heroku: heroku login with email [email protected] and password techRev1w0293057*
  4. Add the staging remote to Git for deploying changes to the staging Heroku environment: git remote add staging [email protected]:mittr-styleguide-staging.git
  5. Commit your changes, or merge them from another banch into master, and deploy them to Heroku staging: git push staging master
  6. Add the production remote to Git for deploying changes to the production Heroku environment: git remote add production [email protected]:mittr-styleguide.git
  7. Commit your changes, or merge them from another banch into master, and deploy them to Heroku production: git push production master

Systems

Notes on the tools and systems used.

  • Gulp is used to automate build and compile processes
  • Node.js is used for generating a micro HTTP server that serves routes and server-side JavaScript
  • Express is a Node web app framework used for MVC routing
  • Nodemon will monitor for any changes in your node.js application and automatically restart the server
  • LiveReload is loaded by Gulp, and is used to for injecting CSS updates into the browser when a /public/less/*.less file is saved
  • Backbone.js
  • Require.js for AMD
  • Swig templating
  • GitHub Flavored Markdown is automatically compiled when used in templates

About

Branding and style guidelines for MIT Technology Review partner and subsidiary sites

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published