fune/devtools/docs
Julian Descottes a9bafec617 Bug 1448077 - move DevTools prefs from libpref/init/all.js to devtools/shared;r=jryans
See RFC https://github.com/devtools-html/rfcs/issues/43

MozReview-Commit-ID: 8YMWCFsJM7A

--HG--
extra : rebase_source : 70a207e256b92a896e8795ec10012d5102add91a
2018-04-06 12:22:53 +02:00
..
backend Bug 1446809 - Remove some b2g leftover in the devtools doc r=jdescottes 2018-03-18 19:30:56 +01:00
contributing Bug 1378108 - Part 2 - Remove Firebug theme;r=gl 2018-04-04 12:32:54 -07:00
files
frontend Backed out 2 changesets (bug 1416024) for failures on browser/base/content/test/performance/browser_startup.js a=backout on a CLOSED TREE 2018-04-05 12:40:08 +03:00
getting-started Bug 1408827 - Where is code link broken for DevTools documentation. r=sole 2017-11-20 23:11:15 -04:00
resources Bug 1234008 - Recompress some png images with zopflipng r=Dolske,Grisha,jryans 2018-01-27 15:57:42 +08:00
styles
tests Bug 1436187 - Move existing shared head files to devtools/client/shared. r=bgrins 2018-03-02 19:14:05 -06:00
tools Bug 1451821 - Put console old-frontend code in webconsole/old; r=jdescottes. 2018-04-06 08:02:58 +02:00
.gitignore
bugs-issues.md
contributing.md
preferences.md Bug 1448077 - move DevTools prefs from libpref/init/all.js to devtools/shared;r=jryans 2018-04-06 12:22:53 +02:00
README.md
SUMMARY.md Bug 1435991 - Document React component best usage r=gregtatum,nchevobbe,ochameau,yulia 2018-03-28 17:19:44 +02: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