[EPIC] REGISTRY

[thinkholic]

• Should have a GitHub Repo named akuru-registry
• All the fonts submission should logged in akuru.json

{
  "name": "",
  "description": "",
  "version": "1.0.0-alpha.0",
  "fonts": [
   {
      "familyName": "Yaldevi",
      "description": "",
      "license": "OFL",
      "designers": [],
      "version": "1.060",
      "foundry": "mooniak",
      "issueTrackerURL": "",
      "srcURL": "",
      "coverImageUrl": "https://raw.githubusercontent.com/fontlet/assets/master/resources/covers/yaldevi.svg?sanitize=true",
      "fontStyles": [
        {
          "styleName": "Regular",
          "fontUrl": "https://github.com/mooniak/yaldevi-fonts/raw/master/fonts/ttf/Yaldevi-Regular.ttf"
        },
        {
          "styleName": "Bold",
          "fontUrl": "https://github.com/mooniak/yaldevi-fonts/raw/master/fonts/ttf/Yaldevi-Bold.ttf"
        },
        {
          "styleName": "ExtraBold",
          "fontUrl": "https://github.com/mooniak/yaldevi-fonts/raw/master/fonts/ttf/Yaldevi-ExtraBold.ttf"
        },
        {
          "styleName": "Medium",
          "fontUrl": "https://github.com/mooniak/yaldevi-fonts/raw/master/fonts/ttf/Yaldevi-Medium.ttf"
        },
        {
          "styleName": "SemiBold",
          "fontUrl": "https://github.com/mooniak/yaldevi-fonts/raw/master/fonts/ttf/Yaldevi-SemiBold.ttf"
        }
      ],
      "tags": [],
    }
  ]
}

• To submit a new font, font developers should send a PR to akuru-registry by updating akuru.json

[pathumego]

Can we maintain the info in TOML or YAML format and build the akuru.json through a CI? It is easier for developers to maintain versions and add more. So we will have a bunch of <family-name>.toml files in registry and we add a new TOML file for each family.

[kasunben]

Yeah, toml/yaml file would be okay. I think it's bette to brainstorming the registry idea further more.