Google Git
Sign in
vanadium / website / 58aa44d67c7e6312421ffdb6f70a0870c6a753cd
commit58aa44d67c7e6312421ffdb6f70a0870c6a753cd[log] [tgz]
authorAli Ghassemi <aghassemi@google.com>Tue Mar 29 10:44:58 2016 -0700
committerAli Ghassemi <aghassemi@google.com>Tue Mar 29 10:44:58 2016 -0700
tree1f3fd0b7cb16a3ba1694116e9b0bac3888a31f46
parent27522ae6703b06d9ff11557ffefdb6969fc04fcc [diff]
TBR: --tmpdir does not exist on OSX, taking a
more platform independent appraoch.

Change-Id: I1954502f988d7f7aad4afb8be3ca4062604cae45
1 file changed
tree: 1f3fd0b7cb16a3ba1694116e9b0bac3888a31f46
  1. browser/
  2. content/
  3. public/
  4. stylesheets/
  5. templates/
  6. test/
  7. tools/
  8. .gitignore
  9. .jiriignore
  10. .jshintignore
  11. .jshintrc
  12. AUTHORS
  13. CONTRIBUTING.md
  14. CONTRIBUTORS
  15. helpers.js
  16. LICENSE
  17. Makefile
  18. package.json
  19. PATENTS
  20. README.md
  21. VERSION
README.md

Vanadium website

This repository contains the source code for generating the static assets for the Vanadium website.

Directory structure

  • browser - Client-side JS that executes when users visit the website
  • build - Output location for make build
  • content - Markdown content; gets converted to HTML by haiku
  • helpers.js - JS used by haiku when rendering Markdown files
  • node_modules - Disposable directory created by npm install
  • package.json - Tells npm install what to install
  • public - Static assets, copied directly into the build directory
  • stylesheets - LESS stylesheets, compiled into CSS for the website
  • templates - Mustache templates used by haiku for layouts and partials
  • tools - Tools involved in generating the site's static assets

Development

Prerequisites

Install Vanadium per the installation instructions on the website. Also, install the Node.js profile using jiri profile install v23:nodejs.

Local development

You can make and view changes locally by running a development server:

make serve

This command will print out a URL to visit in your browser. It will take a few minutes to run the first time around, but subsequent invocations will be fast.

By default, the running server will not reflect subsequent changes to the website content, since it's just serving the assets in the build directory. Running make build will cause the server to see the new content. Better yet, use the following command to automatically rebuild the assets whenever something changes:

make watch

This command requires the entr program, which can be installed on Debian/Ubuntu using apt-get install entr, and on OS X using brew install entr.

Copy changes

Add or modify Markdown-formatted files in the content directory.

The haiku tool provides some extra flexibility on top of standard Markdown by processing Mustache template variables. For example:

= yaml =
title: My Creative Title
author: Alice
= yaml =

# {{ page.title }}

Author: {{ page.author }}

A common editing workflow is to run make watch, edit Markdown files in a text editor, and refresh the browser to see changes. If you prefer a WYSIWYG editing experience, there are a number of options, e.g.:

For new content, it's common to do initial drafting and editing in Google Docs, and to switch to Markdown at publication time.

CSS and JS changes

The make build task generates public/css/bundle.css and public/js/bundle.js from the files in stylesheets and browser respectively. To modify the website CSS or JS, edit those files, then rebuild the site (or use make watch to have your changes trigger rebuild).

Deployment

Jenkins automatically deploys to production on every successful build of vanadium-website-site target.