quartz/layouts/partials/graph.html

<script
  src="https://cdn.jsdelivr.net/npm/d3@6.7.0/dist/d3.min.js"
  integrity="sha256-+7jaYCp29O1JusNWHaYtgUn6EhuP0VaFuswhNV06MyI="
  crossorigin="anonymous"
></script>
<h3>{{ i18n "interactive_graph" }}</h3>
<div id="graph-container"></div>
<style>
  :root {
    --g-node: var(--secondary);
    --g-node-active: var(--primary);
    --g-node-inactive: var(--visited);
    --g-link: var(--outlinegray);
    --g-link-active: #5a7282;
  }
</style>
{{ $js := resources.Get "js/graph.js" | resources.Fingerprint "md5" }}
<script src="{{ $js.Permalink }}"></script>
Add router 2022-05-02 08:06:33 +03:00			`<script`
			`src="https://cdn.jsdelivr.net/npm/d3@6.7.0/dist/d3.min.js"`
			`integrity="sha256-+7jaYCp29O1JusNWHaYtgUn6EhuP0VaFuswhNV06MyI="`
			`crossorigin="anonymous"`
			`></script>`
feat: Add internationalization (i18n) support (#182) 2022-08-24 06:32:40 +03:00			`<h3>{{ i18n "interactive_graph" }}</h3>`
add base structure 2021-07-18 16:35:42 +03:00			`<div id="graph-container"></div>`
			`<style>`
Add router 2022-05-02 08:06:33 +03:00			`:root {`
			`--g-node: var(--secondary);`
			`--g-node-active: var(--primary);`
			`--g-node-inactive: var(--visited);`
			`--g-link: var(--outlinegray);`
			`--g-link-active: #5a7282;`
			`}`
add base structure 2021-07-18 16:35:42 +03:00			`</style>`
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			`{{ $js := resources.Get "js/graph.js" \| resources.Fingerprint "md5" }}`
			`<script src="{{ $js.Permalink }}"></script>`