New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Distribute fonts and css in git repository to make cdnjs work #942
Comments
It will only have Iosevka / Slab / Aile / Etoile, no SS or Term / Fixed variations... |
It'd also be great if the generated css files are minified. Lmk if I can help with anything :) |
Alternatively, I think it is possible for you to set up a repository that holds web font versions of Iosevka, and you can grab its contents from Iosevka Releases using a scheduled workflow. I do not want to maintain "packages" on my own since it will reduce the bandwidth that is used in actual font development. |
@be5invis would you be interested in using GH actions to automate this process? I can come up with a GH actions workflow to build the fonts, tag the release, and push them to another repository. |
I, too, wish there was a repository that just held the most recent release of files. Edit: I'm slightly hijacking this feature request ticket: I wish to be able to just have a repo I can git submodule as part of my dotfiles. Else, I have no other automated way to keep up to date with the file. I'd prefer one that had the Super TTC, as that is what I use now, but I'll take what I can get. Either that, or just the raw Super TTC updated on a webserver that I can just wget and overwrite with. |
Idea: Automate building and publishing the fonts using GitHub actions. We could use GitHub actions to automatically build the fonts, and then push them back to the repository on every commit to master under a directory such as I noticed FiraCode font is doing a similar thing but only uploads the font assets to GitHub actions artifacts. Quick Google search gave me these two actions that would be useful in automating this |
It should be better to set up a new repository that grabs releases of Iosevka and once the version is changed, publish its contents. |
@be5invis Do you mind creating a new repository |
@aymanbagabas I think grabbing releases doesn't need extra auth. It's just an artifact download. |
@be5invis I've created a new repository iosevka-fonts that contains the releases in |
@aymanbagabas LGTM. |
I think this can be closed now since cdnjs/packages#705 is merged. Anyone can use cdnjs and/or JSDelivr to get the fonts from iosevka-fonts as the example below:
Available fonts are |
@be5invis should we add a short blurb under Installation in the readme? |
@aymanbagabas Feels free to submit a PR |
Is your feature request related to a problem? Please describe.
#468
Describe the solution you'd like
Distribute fonts in the Git repository at
dist/{font-variant}/*.(css|ttf|woff2)
Describe alternatives you've considered
Host distributed fonts in a CDN
Additional context
I've created a draft PR for cdnjs/packages cdnjs/packages#685 to add Iosevka to their CDN, however, currently Iosevka does not distribute the fonts in the Git repository rather in Github releases which cdnjs doesn't support.
cdnjs supports either npm/git package distributions. If we can distribute the fonts in a directory along with tagging each release, we would be able to use cdnjs as a free CDN service at the cost of having the fonts and css assets in the repository. cdnjs/packages/CONTRIBUTING
@be5invis what do you think?
The text was updated successfully, but these errors were encountered: