gecko-dev/devtools/docs
Boris Zbarsky 97828fce1d Bug 1415389. Make ChromeUtils a WebIDL namespace. Remove ThreadSafeChromeUtils. r=kmag
MozReview-Commit-ID: 9ysAeaBMNVt
2017-11-08 00:25:33 -05:00
..
backend Bug 1395262 - use plain console.error in devtools promise catches; r=bgrins 2017-08-30 12:05:41 -06:00
contributing Bug 1375800 - [doc] add tips to create a patch file in devtools docs;r=sole 2017-06-23 11:22:49 +02: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 Bug 1395956 - Update gecko.readthedocs links to the new firefox-source-docs.mozilla.org location. r=chutten 2017-09-02 22:11:02 +05:30
getting-started Bug 1395295 - Use 'mach run' where it was intended in the DevTools documentation. r=sole 2017-09-02 00:57:00 -04: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 Bug 1257322 - add more devtools docs r=pbrosset 2016-03-21 10:36:28 -04:00
tests Bug 1399465 - Document DAMP. r=nchevobbe 2017-10-10 16:08:22 +02:00
tools Bug 1415389. Make ChromeUtils a WebIDL namespace. Remove ThreadSafeChromeUtils. r=kmag 2017-11-08 00:25:33 -05:00
.gitignore Bug 1257322 - add more devtools docs r=pbrosset 2016-03-21 10:36:28 -04:00
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 1399465 - Document DAMP. r=nchevobbe 2017-10-10 16:08:22 +02: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
preferences.md Bug 1393767 - add documentation about DevTools preferences;r=sole 2017-08-29 12:06:52 +02: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