Polymer docs are mostly in Markdown with some HTML. Jekyll is used to generate the static HTML for the site. The output is generated into a folder called
_site and served from Google App Engine.
Prereqs and installation requirements
We use Jekyll 2.4 and Grunt to generate the documentation, and compass to compile SASS to CSS. You'll need to install the requirements before working on the docs (these instructions assume NPM is already installed):
gem install bundler npm install -g grunt-cli vulcanize bower
Note: If you receive permission warnings, you may need to run the above tasks with
You'll also need the Python App Engine SDK to run the dev_appserver and preview the docs locally. Download the SDK.
git clone https://github.com/Polymer/docs.git
Making edits and previewing changes
This repo (
Polymer/docs) is where the documentation source files live. To make a change:
- Be sure to run
npm installin your docs directory if it's a new checkout.
- Fire up the
grunttask. This task runs a number of processes: a local app engine server, jekyll, compass, and vulcanize. The jekyll, compass, and vulcanize tasks will all watch for file changes and update the site if you make any edits. Note: Jekyll generates the static site in a folder named
_site. It can take some time for the docs to fully regenerate and be copied to the output folder...keep refreshing!
- Make your edits.
Once your changes look good,
git commit them and push.
Releases: pushing the docs
Note: only project owners can publish the documentation.
It's a good idea to run
grunt before pushing the docs, as it runs a number of grunt tasks. Verify things went well and preview your changes locally using the dev server.
When updating the version of Polymer that the site uses, make sure to also update it in the following apps:
Unzip the release candidate into the
bower_components directory of each app, verify, then run the app's
deploy.sh script. In the case of the Tutorial, you'll need to follow the deploy instructions on the repo itself.
bower update to make sure you have the latest component dependencies.
Once these are updated, you need to update some versions for the docs:
- Increment the version in
- Update the Polymer release version in
- Add a link point link to the release notes in
Build the docs:
At this point, run the dev server with
grunt, and preview things locally to make sure nothing is terribly
broken after Polymer and the elements have been updated.
Next, run the deploy script in the root of the
This script builds the site, api docs, runs Vulcanizer over the imports, and deploys to App Engine.
Last thing is to switch the app version in the App Engine admin console. To make the docs live, hit up https://appengine.google.com/deployment?&app_id=s~polymer-project and select the version you just deployed.