| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
It just adds to network roundtrips. Browser will download them even if they are not used. At least the CSS files will be downloaded (and will actually block other processing!). In some case browser will also download actual font files, even if they are not used, but this will usually be done asynchronously or after page is finished loading. But most of the time it is just a waste of bandwidth (but they are cached for 1y and could be used on other websites).
As a bonus I fixed some quotation issues of urls, because this is what I see in css documentation - https://developer.mozilla.org/en-US/docs/Web/CSS/@import
Next improvement would be to move this `@url import` into separate `link` statement in `base.html`, this way things can proceed in parallel more smoothly.
```html
<link rel="stylesheet" href="https://fonts.googleapis.com/css?subset=latin&family=Crimson+Text:400,400italic,600,600italic,700,700italic" type="text/css" importance="low" referrerpolicy="no-referrer" />
```
After that, and margin all `css` files, this would be really clean and fast theme! :)
PS. Google Fonts Service API allows fetching multiple css files together:
```html
<link rel="stylesheet" href="https://fonts.googleapis.com/css?subset=latin&family=Yanone+Kaffeesatz|Crimson+Text:400,400italic,600,600italic,700,700italic|Droid+Sans+Mono" type="text/css" importance="low" referrerpolicy="no-referrer" />
```
(and similarly using `@import url`).
|
| |
|
|
|
|
| |
We want to populate various HTML metatags from pelican. The data is there, we just have to put in HTML!
To be more precise, the meta names "keywords", "category", "description", "author", "robots" and "date" are taken from pelican variables.
|
