keroosha/keroosha.cybergulag.today
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
25b5ac43dd
keroosha.cybergulag.today/layouts/partials/head.html

47 lines
2.0 KiB
HTML
Raw Normal View History

add base structure
2021-07-18 16:35:42 +03:00
<head>
<!-- Meta tags -->
<meta charset="UTF-8">
popover implementation
2022-01-03 21:18:31 +03:00
<meta name="description" content="{{if .IsHome}}{{$.Site.Data.config.description}}{{else}}{{.Summary}}{{end}}">
proper backlink and graph display in footer
2021-07-18 20:02:53 +03:00
<title>{{ if .Title }}{{ .Title }}{{ else }}{{ $.Site.Data.config.page_title }}{{ end }}</title>
add base structure
2021-07-18 16:35:42 +03:00
<meta name="viewport" content="width=device-width, initial-scale=1">
fix: favicon not showing on non-root domain #89
2022-04-04 03:43:37 +03:00
<link rel="shortcut icon" type="image/png" href="{{$.Site.BaseURL}}/icon.png" />
add base structure
2021-07-18 16:35:42 +03:00
<!-- CSS Stylesheets and Fonts -->
various font and colour fixes
2021-12-26 08:09:15 +03:00
<link href="https://fonts.googleapis.com/css2?family=Inter:wght@400;600;700&family=Source+Sans+Pro:wght@400;600;700&family=Fira+Code:wght@400;700&display=swap" rel="stylesheet">
Move css and js to appropriate files Having the CSS and JS in the html template produces pages larger than necessary, as each page need to contain all the js/css. Separating them in appropriate files allow the browser to just download them once and use them for all the pages. This is even more effective with an aggressive cache policy for the js and css, something that can be done without fear thanks to the implemented cache-busting. Also, having then in separate files allows us to use Hugo pipelines for minimizing the code.
2022-03-04 05:07:51 +03:00
{{$sass := resources.Match "styles/[!_]*.scss" }}
{{$css := slice }}
{{range $sass}}
{{$scss := . | resources.ToCSS (dict "outputStyle" "compressed") }}
{{$css = $css | append $scss}}
add base structure
2021-07-18 16:35:42 +03:00
{{end}}
Move css and js to appropriate files Having the CSS and JS in the html template produces pages larger than necessary, as each page need to contain all the js/css. Separating them in appropriate files allow the browser to just download them once and use them for all the pages. This is even more effective with an aggressive cache policy for the js and css, something that can be done without fear thanks to the implemented cache-busting. Also, having then in separate files allows us to use Hugo pipelines for minimizing the code.
2022-03-04 05:07:51 +03:00
{{$finalCss := $css | resources.Concat "styles.css" | resources.Fingerprint "md5" | resources.Minify }}
<link href="{{$finalCss.Permalink}}" rel="stylesheet">
Execute darkmode script before first render
2021-08-13 23:46:00 +03:00
Move css and js to appropriate files Having the CSS and JS in the html template produces pages larger than necessary, as each page need to contain all the js/css. Separating them in appropriate files allow the browser to just download them once and use them for all the pages. This is even more effective with an aggressive cache policy for the js and css, something that can be done without fear thanks to the implemented cache-busting. Also, having then in separate files allows us to use Hugo pipelines for minimizing the code.
2022-03-04 05:07:51 +03:00
{{ $darkMode := resources.Get "js/darkmode.js" | resources.Fingerprint "md5" | resources.Minify }}
<script src="{{$darkMode.Permalink}}"></script>
feat: basic latex support
2022-04-03 03:00:14 +03:00
{{partial "katex.html" .}}
popover implementation
2022-01-03 21:18:31 +03:00
<!-- Preload page vars -->
Fix fetchData The fetchData function suffer from a race condition. If the function is called before the promise finishes, it will result in another pair of HTTP request. This does not only make the function useless but Actually, it makes it harmful as the data might be redownloaded twice. Now fetchData is not a function but rather the promise by itself. Previous callers are expected to await the variable instead, this should be not concern as awaiting a promise multiple time in JavaScript is completely safe.
2022-03-04 05:25:30 +03:00
{{$linkIndex := resources.Get "indices/linkIndex.json" | resources.Fingerprint "md5" | resources.Minify | }}
{{$contentIndex := resources.Get "indices/contentIndex.json" | resources.Fingerprint "md5" | resources.Minify }}
popover implementation
2022-01-03 21:18:31 +03:00
<script>
Move css and js to appropriate files Having the CSS and JS in the html template produces pages larger than necessary, as each page need to contain all the js/css. Separating them in appropriate files allow the browser to just download them once and use them for all the pages. This is even more effective with an aggressive cache policy for the js and css, something that can be done without fear thanks to the implemented cache-busting. Also, having then in separate files allows us to use Hugo pipelines for minimizing the code.
2022-03-04 05:07:51 +03:00
const BASE_URL = {{.Site.BaseURL}}
Fix fetchData The fetchData function suffer from a race condition. If the function is called before the promise finishes, it will result in another pair of HTTP request. This does not only make the function useless but Actually, it makes it harmful as the data might be redownloaded twice. Now fetchData is not a function but rather the promise by itself. Previous callers are expected to await the variable instead, this should be not concern as awaiting a promise multiple time in JavaScript is completely safe.
2022-03-04 05:25:30 +03:00
const fetchData = Promise.all([
fetch("{{ $linkIndex.Permalink }}")
fix relative pathing for dynamic fetch
2022-02-16 06:54:20 +03:00
.then(data => data.json())
.then(data => ({
index: data.index,
links: data.links,
})),
Fix fetchData The fetchData function suffer from a race condition. If the function is called before the promise finishes, it will result in another pair of HTTP request. This does not only make the function useless but Actually, it makes it harmful as the data might be redownloaded twice. Now fetchData is not a function but rather the promise by itself. Previous callers are expected to await the variable instead, this should be not concern as awaiting a promise multiple time in JavaScript is completely safe.
2022-03-04 05:25:30 +03:00
fetch("{{ $contentIndex.Permalink }}")
fix relative pathing for dynamic fetch
2022-02-16 06:54:20 +03:00
.then(data => data.json()),
Fix fetchData The fetchData function suffer from a race condition. If the function is called before the promise finishes, it will result in another pair of HTTP request. This does not only make the function useless but Actually, it makes it harmful as the data might be redownloaded twice. Now fetchData is not a function but rather the promise by itself. Previous callers are expected to await the variable instead, this should be not concern as awaiting a promise multiple time in JavaScript is completely safe.
2022-03-04 05:25:30 +03:00
])
.then(([{index, links}, content]) => ({
fix relative pathing for dynamic fetch
2022-02-16 06:54:20 +03:00
index,
links,
content,
Fix fetchData The fetchData function suffer from a race condition. If the function is called before the promise finishes, it will result in another pair of HTTP request. This does not only make the function useless but Actually, it makes it harmful as the data might be redownloaded twice. Now fetchData is not a function but rather the promise by itself. Previous callers are expected to await the variable instead, this should be not concern as awaiting a promise multiple time in JavaScript is completely safe.
2022-03-04 05:25:30 +03:00
}))
popover implementation
2022-01-03 21:18:31 +03:00
</script>
more docs + link fixing
2021-07-18 22:19:58 +03:00
</head>
Execute darkmode script before first render
2021-08-13 23:46:00 +03:00
{{ template "_internal/google_analytics.html" . }}
Reference in New Issue Copy Permalink