gecko-dev/devtools/docs
Alexandre Poirot 0f5e860391 Bug 1495551 - Rename all "tab client" occurences to "target front". r=jdescottes
MozReview-Commit-ID: JrEdamUz6Be

Differential Revision: https://phabricator.services.mozilla.com/D8840

--HG--
extra : moz-landing-system : lando
2018-10-16 18:45:33 +00:00
..
backend Bug 1495551 - Rename all "tab client" occurences to "target front". r=jdescottes 2018-10-16 18:45:33 +00:00
contributing Bug 1464782: Update references to offset-* properties in the rest of the tree. r=xidorn 2018-06-27 16:12:02 +02:00
files Bug 1429421 - remove gcli code; r=jdescottes,julienw,ochameau 2018-09-06 11:42:57 +00:00
frontend Bug 1491879 - Fix telemetry support for multiple tabs / windows r=nchevobbe 2018-09-25 12:57:13 +00:00
getting-started Bug 1475474 - Fix broken link to Firefox Build page in devtools-docs;r=sole 2018-07-13 09:02:27 +02: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 1457098 - Update DevTools performance documentation to mention DevTools dashboard;r=ochameau 2018-04-26 12:39:42 +02:00
tools Bug 1172897 - Rename TabActor to BrowsingContextTargetActor. r=ochameau 2018-05-25 18:20:28 -05:00
.gitignore
README.md
SUMMARY.md Bug 1435991 - Document React component best usage r=gregtatum,nchevobbe,ochameau,yulia 2018-03-28 17:19:44 +02:00
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

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