Bikeshed is a pre-processor for spec documents, turning a source document (containing only the actual spec content, plus several shorthands for linking to terms and other things) into a final spec document, with appropriate boilerplate, bibliography, indexes, etc all filled in. It's currently used on nearly all specs in the CSSWG, as well as various specs in the FXTF, SVGWG, WebAppSecurity, WHATWG, and elsewhere!
The processor can be easily installed and run locally (requiring no network access unless you're updating), or accessed as a CGI without any installation at all: https://api.csswg.org/bikeshed/
A short overview of some of Bikeshed's features:
- automatic linking of terms to their definitions based on text, so you can simple write
Use <a>some term</a> to...and have it automatically link to the<dfn>some term</dfn>elsewhere in the document, or in another spec entirely! - automatic id generation for headings and definitions, based on their text.
- textual shortcuts for autolinks: [[FOO]] for bibliography entries, <<foo>> for grammar productions, 'foo' for CSS property names, {{foo}} for IDL terms, and more.
- boilerplate generation, both wholesale and piecemeal.
- partial support for markdown (more is coming, as is compliance with CommonMark).
- a compact syntax for writing property-definition tables.
- automatic whitespace-prefix stripping from
<pre>contents, so the contents can be indented properly in your HTML. - automatic IDL processing and syntax-checking for
<pre class=idl>contents, so you don't have to mark up every single significant term yourself. - automatic generation of railroad diagrams from
<pre class='railroad'>contents.
Bikeshed generates "fatal errors" for lots of things that it wants you to fix,
but generally recovers gracefully from them anyway.
If you're getting a fatal error,
but don't have time to fix it and just need a spec right now,
you can force Bikeshed to generate anyway with the -f flag, like: bikeshed -f spec.
This is also sometimes useful when converting a spec to Bikeshed for the first time,
so you can see all the errors at once and fix them in whatever order is easiest,
rather than having to deal with them one-by-one with no idea when they'll end.
(You may also want to silence the warnings in this case,
to reduce visual noise until you've gotten it at least building successfully.
Use bikeshed -qf spec.)
- Installing Bikeshed - gets you from "reading this page" to "running Bikeshed" in as few steps as possible.
- Quick Start Guide - gets you from an empty file to a full spec in no time.
- Metadata - describes the format of the required metadata block in your spec.
- Definitions, Autolinks, and Bibliography - describes how to create definitions, autolinks, and bibliography entries.
- Markup - describes several of the markup niceties and shortcuts over plain HTML that the processor recognizes.
- Global Names - describes the concept and syntax of global names, which are used by several features to uniquely identify and refer to defined terms.
- IDL - describes Bikeshed's automatic IDL processing.
- Railroad Diagrams - describes the railroad-diagram feature, and its syntax.
- Boilerplate - describes the use and generation of a spec's boilerplate sections. You probably don't need to read this.
- Source-File Processing - describes the functions Bikeshed has for processing your source file itself.
The preferred file extensions for Bikeshed source files is bs, like index.bs.
Bikeshed will automatically recognize *.bs files in the folder it's run in,
and assume that you want an output file of the same name with a .html extension.
The repository also contains a syntax highlighting script for Bikeshed source files.
(Bikeshed also recognizes files with *.src.html for backwards compatibility with older CSS specs,
though most such specs have switched their source file extensions to .bs now.
Using .src.html in most text editors will display the file with HTML source formatting,
which isn't generally what you want.)
This document and all associated files in the github project are licensed under CC0 