jprdonnelly/fonts
1
0
Fork 0
mirror of synced 2025-12-19 17:48:10 -05:00
Code Issues Projects Releases Wiki Activity

Update 1_add-axis.md

Browse Source
This commit is contained in:
Dave Crossland
2023-01-24 01:58:05 -05:00
committed by GitHub
parent 2d2ffc4e36
commit f7a2a8cc5c
1 changed files with 14 additions and 16 deletions
Download Patch File Download Diff File Expand all files Collapse all files

30
.github/ISSUE_TEMPLATE/1_add-axis.md vendored
View File

@@ -1,45 +1,43 @@
---
name: Add Axis
about: Submit a custom axis to Google Fonts Axis Registry.
title: 'Add Axis name [Axis TAG] axis'
title: 'Add (axis name here) [ (AXIS tag here) ] axis'
labels: '--new-axis'
assignees: ''
---
### Font Project introducing the axis
(Provide the name and GitHub repo of the font introducing the axis)
### Short description of what the axis does
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.
Before creating this 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).
### Font project(s) using the axis
(Replace this line with a line or list of the font name(s) and GitHub repo links that already use the axis)
### Short description of what the axis does
(Replace this line with a description of the effect of the axis in the font: What does it operate on (stems, terminals, serifs, etc) and how do changes happen along it?)
### Image
Include here an gif or a video showing the axis behavior.
(Replace this line with a GIF showing the axis behavior from default to min to max to default in a loop)
### Why is the axis needed
Please provide an expected case of use from the user’s point of view, reasoning on why or how the users might use or would benefit from the axis.
This explanation would help to discern the validity of the axis itself and its definitions such as the ranges. This information could be used to create additional educational content.
(Replace this line with 1 or more expected cases, from the user’s point of view, with reasoning on why or how the users can benefit from the axis. This explanation helps the Google Fonts team to discern the validity of the axis itself, and its definitions, such as the ranges. This information could be used to create additional educational content.)
### Axis metadata fields
Complete the following metadata field for the axis.
(Remove this line and fill out the mock of the data structure of the axis)
```
#[Four letter axis TAG] based on (url of the font's repository introducing the axis)
#(replaced this with the four letter AXIS tag) based on (replace this with a URL of the font project repository)
tag: ""
display_name: ""
min_value: