The HTML specification is built using Bikeshed - instructions for installing it are below. Before you create a Pull Request (PR) that is more complex than a simple typo or formatting fix, please update and run bikeshed locally to check that the spec builds correctly.
- Open a command prompt from the HTML repo folder.
- Run: bikeshed update
- Run: bikeshed spec
Bikeshed produces a single page version of the specification. There is also a multi-page script that breaks down the single page version into multiple pages. This relies on node.js - installation instructions are below.
- Run: node multipage.js [path of the spec]
Full installation information is available in the Bikeshed documentation.
Tested on Windows 10.
- Install Python 2.7 (32bit version) in the default location.
- In an elevated command prompt, run: setx /m PATH "%PATH%;C:\Python27;C:\Python27\Scripts"
- Download Pip.py.
- Run
python get-pip.py
where you downloaded the file (??) - Run: c:\python27\python -m pip install pygments lxml==3.6.0 --upgrade
- Clone Bikeshed:
git clone https://github.com/tabatkins/bikeshed.git
or use a desktop client - Run: c:\python27\python -m pip install --editable [path to bikeshed]
- Install Node.JS
- Clone the multi-page repo
- Open a command prompt from the multi-page repo folder and run: npm install
When a change is made to the master branch of the HTML repo, Travis-CI rebuilds the specification and replaces the files in the gh-pages
branch.
You should not edit or commit changes directly on the gh-pages
branch because any changes will be lost when the specification is next rebuilt.