mirror of
https://github.com/welpo/tabi.git
synced 2025-10-11 07:46:15 +02:00
✨ feat: support disabling header font-subset (#458)
Co-authored-by: welpo <welpo@users.noreply.github.com>
This commit is contained in:
parent
162a84b6d6
commit
799f3c0681
9 changed files with 54 additions and 28 deletions
|
@ -1,7 +1,7 @@
|
|||
+++
|
||||
title = "Optimise loading times with a custom font subset"
|
||||
date = 2023-04-29
|
||||
updated = 2023-07-08
|
||||
updated = 2025-01-12
|
||||
description = "Learn how to create a custom subset that only includes the necessary glyphs."
|
||||
|
||||
[taxonomies]
|
||||
|
@ -21,7 +21,11 @@ To fix this, tabi loads a subset of glyphs for the header. Since this (slightly)
|
|||
|
||||
By default, there are subset files for English and Spanish characters (with a few symbols). These files are loaded when the Zola page/site is set to that language.
|
||||
|
||||
For further optimisation, you can create a custom font subset that only includes the characters used in your header.
|
||||
{% admonition(type="tip") %}
|
||||
If you're using a custom font, either create your custom subset (see below) or disable the built-in subsets completely with `enable_subset = false` in your `config.toml`.
|
||||
{% end %}
|
||||
|
||||
Here's how you can create a custom font subset that only includes the characters used in your header, for maximum efficiency.
|
||||
|
||||
## Requirements
|
||||
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue