| Age | Commit message (Collapse) | Author |
|---|
|
|
|
en.yaml translated to Danish
|
|
|
|
|
|
|
|
|
|
|
|
Requested by a user.
See: https://github.com/alanorth/hugo-theme-bootstrap4-blog/issues/145
|
|
|
|
|
|
|
|
We use -O1 instead of --level 1 now.
|
|
|
|
|
|
|
|
We want to build on LTS or "current" releases only.
See: https://nodejs.org/en/about/releases/
|
|
As of 2021-07-01 the Hugo Themes showcase is no longer building our
themes so we need to include a link to a demo.
|
|
This only affects the CI, but the inability to run webpack seems
to have been due to using an older version of npm (v6.14.x), and
now we upgrade npm before install so we don't need this hack.
|
|
It seems that the issue with not being able to find webpack-cli is
due to some behavior with an older version of npm. My local devel-
opment environment has npm 7.6.x and so does the Node.js 15 conta-
iner, while the Node.js 12 and 14 containers have npm 6.14.x.
Updating npm fixes the issue with `npx webpack` not being able to
find webpack-cli's webpack command (perhaps it installs the peer
dependency automatically, I don't know).
|
|
My local dev environment automatically adds ./node_modules/.bin to
the shell PATH, but it seems a better way to do this is to use npx
so that it works here and on the CI.
|
|
Node.js v10 will cease to be LTS next month and I haven't even used
it for a while already, so let's change this to only run on 12, 14,
and 15, which are the current active and LTS releases.
See: https://nodejs.org/en/about/releases/
|
|
|
|
We don't explicitly need webpack, as webpack-cli will bring it in
for us.
|
|
|
|
|
|
Minor, but can be very confusing when looking at CSS and wondering
why the version is old.
|
|
Brings in Bootstrap v4.6.0 as well as a few others.
|
|
|
|
TravisCI changed their business model recently and I realized it is
better to not rely on free cloud services. I am now using a Drone.io
instance on my own infrastructure.
|
|
|
|
|
|
|
|
|
|
|
|
These are the second generation of Amazon's ARM-based instances.
See: https://blog.travis-ci.com/2020-09-11-arm-on-aws
|
|
|
|
|
|
|
|
The Hugo internal Twitter and OpenGraph templates assume your post
images are in the static directory. This tries to look them up in
the page bundle first and falls back to the Hugo default behavior.
|
|
This overrides Hugo's default figure shortcode to enable img srcset
support, which allows the client to decide which size of image they
want to download based on a CSS media query. During build time Hugo
creates several versions of each image to match several breakpoints.
Unfortunately this only works if the images are in the post's page
bundle, falling back to retrieving images from the static directory
if they aren't found in the bundle.
This shortcode was originally from Charl P. Botha, but I modified
it to automatically rotate images that have orientation EXIF data.
See: https://gohugo.io/content-management/page-bundles/
See: http://www.johann-oberdorfer.eu/blog/2020/01/05/20-01-05_leverage_page_bundles_in_hugo/
See: https://cpbotha.net/2020/05/02/drop-in-replacement-for-hugo-figure-shortcode-with-responsive-img-srcset/
|
|
|
|
|
|
Imports are relative to the current file it seems.
|
|
libsass (and therefore node-sass) is deprecated and dart sass is
recommended.
See: https://sass-lang.com/blog/libsass-is-deprecated
|
|
|
|
It's more current and it's the one that is using this theme anyway.
|
|
|
|
|
|
|
|
|
