-
Notifications
You must be signed in to change notification settings - Fork 41
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
Request for custom web fonts support #7
Comments
Hi, @B-Interactive! Thanks for your question. See https://github.com/willfaught/paige#include. You'll want to create a Please let me know if the include section in the readme was unclear about how it works, or why you'd want to use it. It's a work in progress. |
Ah! That's exactly what I needed, that's great! I come from WordPress, so I'm looking for ways to hook in code, and there it is, laid out beautifully, thank you. |
Hugo is still pretty new territory for me, so please let me know if I've approached this the wrong way. That said, I have hunted for an official way, or best practice for making use of web fonts, but standard method seems to be entirely missing.
That is, it seems it's open to theme developers to implement this, should they choose to.
At the moment, in order to make updating the theme simpler, I've resorted to overriding only the head.html partial. I modify it to point to
paige/myLinks.html
andpaige/myStyle.html
, instead of the originalpaige/links.html
andpaige/style.html
partials respectively.Having created those files, they then reference the original partials, so any theme updates to those are sustained, but it still permits me to include my custom additions:
paige/myLinks.html
paige/myStyle.html
Whilst this is working, theme updates to
/themes/paige/layouts/partials/paige/head.html
will be missed unless I manually review it each time. I wonder you might consider a more elegant way to reference web fonts with theme support, within config.toml / .yaml, etc.The text was updated successfully, but these errors were encountered: