refactor!: replace header, drawer, and footer, with shortcodes #31
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
refactor!: replace header, drawer, and footer with shortcodes
Previously, the layout of the header, drawer, and footer were dictated by template partials, which were driven with markup encoded in the yaml frontmatter. This severely restricted the layout and content in each of these elements:
These elements are now replaced with
{{<header>}}
,{{<aside>}}
and{{<footer>}}
, which may be placed in the resume markup. Each element only serves to render and place the contained markup in the corresponding location of the page.{{<entry>}}
with### h3
and{{<date-range>}}
Previously, each resume entry required a shortcode that dictated the layout of a name, affiliation, date-range, and a description rendered to markdown. This severely restricted and unnecessarily complicated the layout and content of the main portion of the resume.
Now,
{{<entry>}}
has been removed, but can be closely emulated with a combination anh3
(###) header, a{{<date-range>}}
, and any content that follows these. See the changes tocontent/_index.md
for more details on how this migration may be done.A draw-back up of this method is that the entry affiliation may no longer be placed on a separate line from the position name, however, support for this could be added using an
#### h4
. I'll do this if there's demand for it.Images supplied as markdown can now reference bitmaps or svgs. In the former case, the supplied bitmap image is used to generate a srcset of responsive images. In the latter case, the supplied svg will be embedded directly into the html, as
Bitmap images provided in the markdown, are now used to generate a srcset of responsive images. All configurations related to this process can be controlled with hugo attributes. See
layouts/_default/_markup/render-image.html
and the changes tocontent_index.md
for more details on how this is done.They were missing...I don't know why.
Date ranges are normally placed to the right of an h3, but the text wasn't aligned due to a difference in font sizes. All elements in the main grid are now aligned with their baselines.
65464b7 previously removed a failed attempt at preventing page breaks inside entries. We make a new attempt at this by setting
break-before: avoid
on all children of the{{<main>}}
element, except for h3 headers and {{}} shortcodes.refactor(txt): stop uppercase-ing section titles
refactor: prioritize page title over site title
Previously, the title in a page's frontmatter would be ignored. Now, this title is read in head.html and is prioritized over the site title.
chore: add dev:tailscale script
This commit adds support for using Tailscale to serve the website to the rest of my tailnet.
The motivation for this change was to be able to view the live site on my phone during development.
Note that while Hugo can serve locally with SSL certs, this also uses Tailscale to generate certificates, as it will also distribute them.