From: Viviana Monsalve Date: Mon, 23 Jan 2023 18:25:56 +0000 (-0500) Subject: Requirements poiting to Protocol added X-Git-Tag: v0.4.0~4^2~2 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=6f24682fedfeb6281078c5f457c02eb6d0bbf17f;p=thirdparty%2Fgoogle%2Ffonts.git Requirements poiting to Protocol added --- diff --git a/.github/ISSUE_TEMPLATE/1_add-axis.md b/.github/ISSUE_TEMPLATE/1_add-axis.md index a0e558f290..7cad502aa7 100644 --- a/.github/ISSUE_TEMPLATE/1_add-axis.md +++ b/.github/ISSUE_TEMPLATE/1_add-axis.md @@ -15,6 +15,15 @@ assignees: '' Describe the effect of the axis in the font. Over what does it operates (stems, terminals, serifs, etc) how changes happen. +### Requirements + +Before creating a new issue to propose a new custom axis, you should read the [Axis Registry Protocol](https://googlefonts.github.io/gf-guide/axis-registry.html) in the Production chapter of the GF-Guide. It provides the required steps for including a new axis (prior to creating this Issue), as well as detailed information on the axis requirements and the type of axes that would inform your decisions on the required Metadata Fields. + +By ticking the cases (or putting x between the square brackets in text mode), you confirm the following: + +- [ ] I have inspected the current [Axis Registry](https://github.com/googlefonts/axisregistry/tree/main/Lib/axisregistry/data) and there is not a registered custom axis that could be used for the variation purpose on the upcoming font project. +- [ ] The metadata fields of the proposed axis meet the *Axis Requirements* as specified in the Protocol (linked above). + ### Image Attach here a pic or a gif showing the axis behavior.