gecko-dev/devtools/docs
sole 8c22801540 Bug 1365255 - DevTools: bring over documentation for contributing and coding standards into the tree. r=nchevobbe
MozReview-Commit-ID: IRtCRTMmPHu

--HG--
extra : rebase_source : df1a6325a746a6408159b9f8223d82748ca27c13
2017-05-26 13:02:02 +01:00
..
backend
contributing Bug 1365255 - DevTools: bring over documentation for contributing and coding standards into the tree. r=nchevobbe 2017-05-26 13:02:02 +01:00
files Bug 1365216 - DevTools: bring over documentation for how to find documentation into the tree. r=pbro 2017-05-16 13:18:48 +01:00
frontend
getting-started Bug 1365216 - Follow up. r=pbro 2017-05-17 16:06:07 +01:00
resources Bug 1365216 - DevTools: bring over documentation for how to find documentation into the tree. r=pbro 2017-05-16 13:18:48 +01:00
styles
tests Bug 1365255 - DevTools: bring over documentation for contributing and coding standards into the tree. r=nchevobbe 2017-05-26 13:02:02 +01:00
tools
.gitignore
README.md Bug 1365216 - DevTools: bring over documentation for how to find documentation into the tree. r=pbro 2017-05-16 13:18:48 +01:00
SUMMARY.md Bug 1365255 - DevTools: bring over documentation for contributing and coding standards into the tree. r=nchevobbe 2017-05-26 13:02:02 +01:00
bugs-issues.md Bug 1365216 - DevTools: bring over documentation for how to find documentation into the tree. r=pbro 2017-05-16 13:18:48 +01:00
contributing.md Bug 1365255 - DevTools: bring over documentation for contributing and coding standards into the tree. r=nchevobbe 2017-05-26 13:02:02 +01:00

README.md

Firefox Developer Tools

Hello!

This documentation is for developers who want to work on the developer tools. Get started here.

If you are looking for end user documentation, check out this MDN page instead.

Happy developing!

About this documentation

This guide is built with MarkDown files and GitBook.

The source code for this documentation is distributed with the source code for the tools, in the docs/ folder.

If you want to contribute to the documentation, clone the repository, make your changes locally, and then regenerate the book to see how it looks like before submitting a patch:

# Install GitBook locally
npm install -g gitbook-cli

# Go into the docs directory
cd /path/to/mozilla-central/devtools/docs/

# Generate the docs and start a local server
gitbook serve

# You can now navigate to localhost:4000 to see the output

# Or build the book only (this places the output into `docs/_book`)
gitbook build