A tool for creating technical documents and web standards
Clone or download
Latest commit df6bba4 Sep 17, 2018
Failed to load latest commit information.
builds v23.0.3 Sep 17, 2018
examples v23.0.1 Sep 15, 2018
js fix(profile-w3c-common): URL params no longer a depedency Sep 15, 2018
src fix(core/structure): toc heading must have id (#1829) Sep 17, 2018
tests fix(core/structure): toc heading must have id (#1829) Sep 17, 2018
tools fix(tools/copydeps): dont copy URL params Sep 15, 2018
worker fix(worker/respec-worker): offline error-handling Jul 17, 2017
.babelrc BREAKING CHANGE: use jQuery slim (#1432) Nov 18, 2017
.editorconfig Changed to use 2 instead of 4 spaces Mar 2, 2016
.eslintrc.json refactor: remove `var` (#1784) Jul 30, 2018
.gitignore chore(.gitignore): use globs (#1518) Feb 19, 2018
.jscsrc Fix(jscs): esnext rule was removed from 3.0 Apr 15, 2016
.jshintrc chore(deps): move dependencies to js/deps (closes #633) Jun 17, 2016
.npmignore chore(.npmignore): ignore .vs dir Jun 26, 2018
.snyk fix: package.json & .snyk to reduce vulnerabilities Oct 26, 2017
.travis.yml Force eslint (#1777) Jul 28, 2018
.vscode chore(.vscode): add Visual Studio config Jul 5, 2017
CHANGELOG.md chore(CHANGELOG): regenerate Jun 26, 2018
CODE_OF_CONDUCT.md docs: http -> https (#1190) Apr 30, 2017
ISSUE_TEMPLATE.md docs(ISSUE_TEMPLATE): fix template Apr 23, 2018
LICENSE.md chore(LICENSE): add LICENSE.md file (closes #1317) Jul 17, 2017
README.md Docs: fix link to editor's guide Feb 13, 2018
karma.conf.js fix(templates/show-people): allow HTML for company field (#1790) Aug 1, 2018
package-lock.json v23.0.3 Sep 17, 2018
package.json v23.0.3 Sep 17, 2018
yarn.lock chore(yarn): update lock file Oct 23, 2017



Greenkeeper badge Build Status Known Vulnerabilities

ReSpec is a JS library that makes it easier to write technical specifications, or documents that tend to be technical in nature in general. It was originally designed for the purpose of writing W3C specifications, but has since grown to be able to support other outputs as well.

Getting started

If you are just interested in writing a spec, you can grab the starter spec.

We have extensive documentation on how to use ReSpec in our wiki, including:

You don't need to check-out or fork this repository.

If you are new to spec writing, we strongly encourage you to read:

Getting help

If you experience issues, please email spec-prod@w3.org or if you think something is broken, file a bug.

Please note: ReSpec is not endorsed by W3C and nobody should expect the W3C Webmaster to provide advice on problems encountered with ReSpec, or on why it may be failing to produce pubrules-compliant content.

Bibliographical references

Bibliographical references have been moved out of ReSpec. You want to use specref.org.

Want to see complete documentation?

Documentation for ReSpec is available in our wiki.


Please see our developer guide.

Please note that this project is released with a Contributor Code of Conduct. By participating in this project you agree to abide by its terms.