gecko-dev/devtools/docs
sole 8efc1bf877 Bug 1365216 - Follow up. r=pbro
MozReview-Commit-ID: 9X9xSaxTQkB

--HG--
extra : rebase_source : 5b213ab74e9c9977f38e0cb9b263625e9f601844
2017-05-17 16:06:07 +01:00
..
backend Bug 1361710 - Move the debugger client API doc to the tree; r=sole 2017-05-03 15:35:17 +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 1357704 - Create documentation for scalars in Telemetry.js r=sole 2017-04-19 12:48:24 +01:00
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 Bug 1257322 - add more devtools docs r=pbrosset 2016-03-21 10:36:28 -04:00
tests Bug 1364453 - DevTools: move debugging intermittents documentation into the tree. r=pbro 2017-05-12 16:19:43 +01:00
tools Bug 1352049 - Network panel documentation;r=Honza,rickychien 2017-04-10 15:51:24 +08: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 1365216 - Follow up. r=pbro 2017-05-17 16:06:07 +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

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