Update docs once gftools builder is merged

[m4rc1e]

Would be nice to get people using gftools builder once it is merged.

googlefonts/gftools#278

[RosaWagner]

Agreed

[davelab6]

I think there should be a few fb checks for upstream repo structure, readme contents, etc, but something fancy that would be nice to check is a "fonts in use" or "title card" in the repo readme, like https://css-tricks.com/custom-styles-in-github-readmes/

[m4rc1e]

Do we have an FB upstream profile? it may be quite nice to have one.

cc @felipesanches

[davelab6]

Now it's merged, it would be great to update the Spec doc soon. As @moyogo is "new" I propose you to do this, what do you think? :)

[moyogo]

Should all the argument be available at the command line?
For example:

usage: gftools-builder.py [-h] [--debug] [--log-level LOG_LEVEL] [--stylespace-file STYLESPACE_FILE] [--stat STAT] [--build-variable BUILD_VARIABLE] [--build-static BUILD_STATIC]
                          [--build-webfont BUILD_WEBFONT] [--output-dir OUTPUT_DIR] [--vf-dir VF_DIR] [--tt-dir TT_DIR] [--ot-dir OT_DIR] [--woff-dir WOFF_DIR] [--autohint-t-t-f AUTOHINT_T_T_F]
                          [--axis-order AXIS_ORDER] [--family-name FAMILY_NAME] [--no-autohint] [--stylespace STYLESPACE]
                          file [file ...]

[davelab6]

Do you mean it's more elegant to require a config.yaml or whatever and only pass that 1 arg to the tool? It's reach across a lot of sub processes means a lot of args seems inevitable to me....

[m4rc1e]

Personally, I'd prefer if we kept the current minimal set of args. This will then ensure that people actually bother to make a config file and not just pass in arbitrary cmd line args each time they gen.