gecko-dev/devtools/docs
Michael Ratcliffe b23784ee71 Bug 1441070 - Instrument toolbox panel navigation with event telemetry r=yulia
This is pretty simple... finding the best locations for the probes was the
struggle here.

In order to land these probes before the freeze the test for these events will
be created as part of bug 1456073.

MozReview-Commit-ID: 7hIfbD3wQ1I

--HG--
extra : rebase_source : 990e69e0816742fc306b9313bd113f2d71f00b72
2018-04-19 12:09:28 +01:00
..
backend Bug 1446809 - Remove some b2g leftover in the devtools doc r=jdescottes 2018-03-18 19:30:56 +01:00
contributing Bug 1454350 - simplify devtools docs to use mercurial. r=sole 2018-04-16 14:53:58 +02:00
files
frontend Bug 1441070 - Instrument toolbox panel navigation with event telemetry r=yulia 2018-04-19 12:09:28 +01:00
getting-started Bug 1454350 - simplify devtools docs to use mercurial. r=sole 2018-04-16 14:53:58 +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 1454582 - Update docs with new job name (damp-e10s) to run DAMP tests on try. r=jdescottes 2018-04-17 01:18:14 -07: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