gecko-dev/devtools/docs
Alexandre Poirot 4e2dcbf894 Bug 1415545 - Document working on DevTools performance. r=sole
MozReview-Commit-ID: 4N0Kx7PO4Xc

--HG--
extra : rebase_source : 5c9b6952419984a577038b14b72746dc069daf0c
2017-12-13 09:58:23 -08:00
..
backend Bug 1416711 - Add registerAllActors API;r=ochameau 2017-11-13 21:22:15 +01:00
contributing Bug 1415545 - Document working on DevTools performance. r=sole 2017-12-13 09:58:23 -08:00
files
frontend
getting-started Bug 1408827 - Where is code link broken for DevTools documentation. r=sole 2017-11-20 23:11:15 -04:00
resources
styles
tests Bug 1415472 - Document writing new DAMP test. r=sole 2017-12-11 06:07:10 -08:00
tools Bug 1415389. Make ChromeUtils a WebIDL namespace. Remove ThreadSafeChromeUtils. r=kmag 2017-11-08 00:25:33 -05:00
.gitignore
bugs-issues.md
contributing.md
preferences.md
README.md
SUMMARY.md Bug 1415545 - Document working on DevTools performance. r=sole 2017-12-13 09:58:23 -08:00

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