Repository for public analyses.
Перейти к файлу
Jason Thomas cc96e0ea4b
Update references for default branch rename (#119)
2021-04-06 14:24:49 -07:00
.circleci Update references for default branch rename (#119) 2021-04-06 14:24:49 -07:00
addons Move static content into the repository 2018-10-24 13:57:07 -04:00
bug1381516.kp Move static content into the repository 2018-10-24 13:57:07 -04:00
e10s_analyses/beta/51
etl Bug 1571462 - Remove mobile_clients job 2019-09-30 16:02:49 +02:00
examples/new_report.kp Move static content into the repository 2018-10-24 13:57:07 -04:00
projects Webrender Fenix performance study (#117) 2020-06-08 09:26:45 -07:00
script Bug 1501814 - Switch publishing from Knowledge Repo to Docere 2019-03-21 12:49:12 -04:00
static/legacy/knowledge-repo Move static content into the repository 2018-10-24 13:57:07 -04:00
testpilot TxP Side View Experiment final report 2019-04-02 14:36:11 -04:00
tutorials Move static content into the repository 2018-10-24 13:57:07 -04:00
.gitignore
CODE_OF_CONDUCT.md Add Mozilla Code of Conduct file 2019-04-01 16:47:11 -07:00
README.md Update references for default branch rename (#119) 2021-04-06 14:24:49 -07:00

README.md

Mozilla Reports

This repository contains public data analyses.

You can find the rendered reports at:

Adding a new report

First, fork this repository and clone the fork locally. Be sure to set the upstream remote:

git remote add upstream git@github.com:mozilla/mozilla-reports.git

Copy your report

Once you have a local copy of the repository, copy your report to a new directory in this repository. For example, if you have an analysis in ~/Documents/user_count/:

cd mozilla-private-reports
cp -r ~/Documents/user_count ./user_count

Your report is copied to the rendered site without any modifications. Be sure that your analysis directory contains a fully rendered copy of your report

The entire directory is included in the rendered site, so your report can be comprised of multiple pages

Add metadata

Add a report.json file to your new directory. This registers your index.html file as a report and provides metadata necessary for generating the index pages.

The required fields are documented in docere's documentation: Here's a minimal example:

{
  "title": "User Count Report",
  "publish_date": "2018-03-01",
  "author": "Wadley Hickam"
}

By default, docere looks links to an index.html file in your report directory. You can override this by specifying a "file" key to report.json

Preview your changes

We use docere to generate metadata pages for these reports.

Make sure you have a python environment with docere installed:

python3 -m venv venv
source venv/bin/active
pip install docere

And then you can preview content by invoking:

./script/render.sh
firefox site/index.html

Publish

To publish your report, create a pull request and get review. Once your report is merged to main, it will automatically be pushed to [dev RTMO]

For example, using GitHub's CLI, hub:

git add .
git checkout -b user_count_report
git commit -am "Add user count report"
git push -u origin user_count_report
hub pull-request