A guide for Mozilla's developers and data scientists to analyze and interpret the data gathered by our data collection systems.
Перейти к файлу
Ryan Harter 654a9c81df Fix broken links 2017-07-20 15:29:38 -04:00
assets Add Roberto's data pipeline page (#20) 2017-06-02 13:12:09 -04:00
concepts Fix broken links 2017-07-20 15:29:38 -04:00
cookbooks Fix broken links 2017-07-20 15:29:38 -04:00
datasets Revise spark.md, fix broken addons link 2017-06-15 12:08:19 -04:00
meta Provide README for contributing documentation 2017-02-28 12:20:34 -05:00
scripts Add "Custom Analysis with Spark" and pandoc script 2017-06-15 12:08:19 -04:00
tools Revise spark.md, fix broken addons link 2017-06-15 12:08:19 -04:00
.gitignore Revise Choosing a Dataset to standard format 2017-04-20 13:07:17 -04:00
README.md Fix broken links and add process notes 2017-03-29 17:54:25 -04:00
SUMMARY.md Update SUMMARY to include new create_a_dataset 2017-06-16 12:06:32 -04:00
book.json Revise Choosing a Dataset to standard format 2017-04-20 13:07:17 -04:00
introduction.md Add bug template for new docs, delete bad links 2017-06-05 12:54:23 -04:00

README.md

Firefox Data Documentation

This document will teach you how to answer questions about Firefox Users with data. You can find the rendered documentation here.

This documentation is rendered with GitBook, and hosted on Github pages.

Building the documentation

To build the documentation locally, you'll need to install the gitbook-cli app with npm:

npm install gitbook-cli -g

You can then clone the repository and serve the documentation locally with:

gitbook serve

The complete documentation for the gitbook toolchain is at: https://toolchain.gitbook.com/.

Adding a new article

This documentation is under active development, so we may already be working on the documentation you need. Take a look at this bug tree to check. Please open a new bug if you spot any missing documentation.

Articles can be written in either Markdown or AsciiDoc. I recommend using Markdown by default. If you run into any technical limitations, let me (@harter) know. I'm happy to change the tooling to make it as much fun as possible to write.

Be sure to link to your new article from SUMMARY.md, or GitBook will not render the file.

Review

Once your happy with your contribution, please open a PR and flag @harterrt for review. Please squash your changes into meaningful commits and follow these commit message guidelines.

I'll give it review for clarity. This documentation is meant to address higher level concepts, so I'm aiming to keep a conversational tone throughout the document. Beyond that, I don't have a strong opinion. If you'd find it helpful, we have some consumers of this documentation who have agreed to review PRs for clairty. This will give you a fresh set of eyes to identify any jargon or difficult to understand sections.