Update docs once gftools builder is merged
Opened this issue · 7 comments
Would be nice to get people using gftools builder
once it is merged.
Agreed
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/
Do we have an FB upstream profile? it may be quite nice to have one.
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? :)
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 ...]
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.