alanorth/hugo-theme-bootstrap4-blog
1
0
Fork 0
mirror of https://github.com/alanorth/hugo-theme-bootstrap4-blog.git synced 2024-12-19 00:52:19 +01:00
Code Releases Activity
619 Commits 1 Branch 21 Tags 4.6 MiB
54d3242633
Commit Graph

619 Commits

This Branch
This Branch
All Branches
Author SHA1 Message Date
Alan Orth
4b2b1617c0
Regenerate static assets 2020-10-09 23:18:48 +03:00
Alan Orth
415ae8956c
source/scss/bootstrap.scss: Bump version to 4.5.2 
This is only a comment but it shows in the generated CSS and can be
confusing when you are expecting to see one number, but see another.
 2020-10-09 23:17:45 +03:00
Alan Orth
3987192a31
Run npm update 2020-10-09 23:16:45 +03:00
Alan Orth
3254306148
.travis.yml: Node.js 15 isn't released yet 
See: https://nodejs.org/en/about/releases/
 2020-07-27 15:40:55 +03:00
Alan Orth
536dd793fe
.travis.yml: Add current Node.js versions 
See: https://nodejs.org/en/about/releases/
 2020-07-27 15:38:55 +03:00
Alan Orth
9b877752b7
Version 1.5.0 2020-05-17 22:48:58 +03:00
Alan Orth
ef714f2192
layouts: Fix error in Haven invocation 2020-05-17 22:45:23 +03:00
Alan Orth
d72552cde3
layouts: Update Haven invocation 
If the user has configured a cookie consent information URL we will
show it in the banner.
 2020-05-17 22:42:56 +03:00
Alan Orth
21aab8a79d
README.md: Update Google Analytics description 
Now consent is mandatory if you enable Google Analytics.
 2020-05-17 22:40:32 +03:00
Alan Orth
26f170bfdd
layouts: Test for existence of Google Analytics ID 
Previously we showed the Cookie Usage banner if the site's config
had a cookie consent URL specified. As of 2018-05 (GDPR) it makes
more sense to only display this banner if the site has a Google
Analytics ID set. Because we are using Haven for consent manage-
ment we can now inject Google Analytics automatically after the
user has agreed, so we no longer need to use Hugo's internal te-
mplate.
 2020-05-17 22:32:12 +03:00
Alan Orth
dedea8ccc0
README.md: Update feature description for Google Analytics 2020-05-17 22:26:24 +03:00
Alan Orth
006e3f49bd
CHANGELOG.md: Move unreleased changes to v1.5.0 2020-05-17 22:24:52 +03:00
Alan Orth
a019ed776f
CHANGELOG.md: Add note about Haven 2020-05-13 14:19:04 +03:00
Alan Orth
3b360d2eef
Use haven for GDPR popup instead of cookieconsent 
Haven is newer and more well maintained (and also it is actually
open source instead of open core with an upsell to a paid subscrip-
tion). Haven is configured to be 100% *opt-in* for Google Analytics,
which means it does not load or send a hit until the user agrees.

This is mostly a drop-in replacement, but translations need to make
sure the following strings are updated:

- cookieAccept
- cookieDecline
 2020-05-13 13:19:41 +03:00
Alan Orth
e840f783e7
CHANGELOG: Add unreleased changes 2020-05-13 10:01:18 +03:00
Alan Orth
8da96f34ef
Regenerate static assets 2020-05-13 10:00:27 +03:00
Alan Orth
2845e18f9a
package.json: Run npm update 
Minor version bumps to webpack, fontawesome, and node-sass.
 2020-05-13 09:58:50 +03:00
Alan Orth
8448af2481
Bootstrap v4.5.0 
See: https://github.com/twbs/bootstrap/releases/tag/v4.5.0
 2020-05-13 09:54:43 +03:00
Alan Orth
a390958117
Revert ".travis.yml: Use an LXD container instead of VM" 
This reverts commit faa3c3cf5b.

Build took over six minutes for each Node.js version because NVM
had to build each from source. So yeah, let's go back to amd64 VMs.
 2020-03-30 09:31:34 +03:00
Alan Orth
faa3c3cf5b
.travis.yml: Use an LXD container instead of VM 
We need to specify OS and Arch in order to use an LXD container in-
stead of a VM. This should theoretically be much faster according
to the Travis docs. Here we are building on arm64 because there is
no amd64 container support right now, but it shouldn't matter beca-
use we are only doing npm build.

See: https://docs.travis-ci.com/user/reference/overview/
 2020-03-30 09:16:38 +03:00
Alan Orth
bbc5ef18cf
.travis.yml: Don't use Node.js v14 
It is not released yet.

See: https://nodejs.org/en/about/releases/
 2020-03-29 16:49:49 +03:00
Alan Orth
1cb082e1f1
.travis.yml: Update 
Remove deprecated sudo, update Node.js versions to current actively
maintained and LTS versions, use Ubuntu 18.04 "Bionic" environment
instead of 16.04 "Xenial".
 2020-03-29 16:44:33 +03:00
Alan Orth
3a83d4e43e
CHANGELOG.md: Add note about DE i18n strings 2020-03-25 14:18:53 +02:00
Marcel Mellor
3c21de9fcd Added missing language keys DE 2020-03-25 14:16:49 +02:00
Alan Orth
ce89342827
exampleSite/config.toml: Show how to override date format 2020-03-22 15:28:33 +02:00
Alan Orth
a2ac9fe29e
CHANGELOG.md: Update cookieconsent to 3.1.1 2020-03-22 15:10:23 +02:00
Alan Orth
77e05f010e
Regenerate static asssets 2020-03-22 15:09:46 +02:00
Alan Orth
320ee71b75
Update to cookieconsent 3.1.1 
In my minimal testing this works for the default popup.
 2020-03-22 15:09:01 +02:00
Alan Orth
9bbfab2f1b
Version 1.4.2 2020-03-22 11:17:27 +02:00
Alan Orth
f7d9451aa6
layouts: Fix minor encoding issue with dates 
This is similar to other encoding issues we have fixed lately where
we need to make sure Hugo (or Golang's HTML template library) does
not escape our non-ASCII content.

For example, this is how our datetimes end up currently:

    <p class="blog-post-meta"><time datetime="2020-01-16T09:23:20&#43;02:00">Thu Jan 16, 2020</time> by Alan Orth

After printing them with `printf` and filtering them with the Hugo
built-in function `safeHTMLAttr` they look like this:

    <p class="blog-post-meta"><time datetime="2020-01-16T09:23:20+02:00">Thu Jan 16, 2020</time> by Alan Orth

See: https://github.com/gohugoio/hugo/blob/master/tpl/tplimpl/embedded/templates/opengraph.html
See: https://github.com/alanorth/hugo-theme-bootstrap4-blog/pull/111
 2020-03-22 11:09:27 +02:00
Alan Orth
85abd20ba7
layouts: Fix more structured data escaping issues 
I think we actually only need to quote string literals. Otherwise,
it seems that Hugo automatically adds quoting for us, and doesn't
use funny escaping of URLs, special characters, etc.
 2020-03-19 15:45:31 +02:00
Alan Orth
9e0b00038a
Version 1.4.1 
And oops, I had forgotten to bump the version in package.json for
v1.4.0.
 2020-03-19 15:29:30 +02:00
Alan Orth
9676a9736b
CHANGELOG.md: Add note about fix for structured data 2020-03-19 15:27:51 +02:00
Alan Orth
4a88be4434
layouts: Remove quoting of structured data 
I don't understand it, but quoting these values causes Hugo to use
escape codes for non-ASCII (?) characters. For example:

  "description": "A thriving oasis in Jordan\x27s desert is at risk of disappearing."

Google's Search Console shows the following error:

    Unparsable structured data > Bad escape sequence in string

We had a similar issue with dates that was fixed in #111 and the
solution is the same here.
 2020-03-19 15:22:29 +02:00
Alan Orth
780444bfb0
README.md: Add note about Farsi 2020-03-16 11:57:37 +02:00
Alan Orth
58d01baba6
CHANGELOG.md: Add note about updated dependencies 2020-03-16 09:49:32 +02:00
Alan Orth
9fb0baa0a5
Regenerate static assets 2020-03-16 09:47:25 +02:00
Alan Orth
550b5c066d
Run npm update 
Brings new versions of rtlcss, webpack, and fontawesome.
 2020-03-16 09:46:39 +02:00
Alan Orth
3be21cba1d
CHANGELOG.md: Adjust headings 2020-01-28 11:06:03 +02:00
Alan Orth
ce3e6a933f
CHANGELOG.md: Release v1.4.0 2020-01-28 11:01:34 +02:00
Alan Orth
22001d38ea
CHANGELOG.md: Update notes for unreleased version 2020-01-28 10:59:46 +02:00
Alan Orth
d4ece493ba
layouts/partials/meta-terms.html: Trailing slash 
Hard code a trailing slash in URLs for categories and tags to avoid
an HTTP 301 redirect at the very least, and an HTTP 404 at the very
worst (depending on web server configuration).

This is a workaround for a problem caused by our manual construction
of URLs using the categories and tags strings in post front matter.
Hugo's own taxonomy tooling always uses a trailing slash.

See: https://github.com/alanorth/hugo-theme-bootstrap4-blog/issues/128
 2020-01-28 10:50:31 +02:00
Alan Orth
3ab60bddea
Use Font Awesome SVGs via JavaScript 
This is a bit of "one step forward, two steps back" in that we are
now using the much more lean SVG icons—and only the ones we are ac
tually using—instead of having to download the two ~70KiB web font
files, but it means we need to use JavaScript.

This approache was inspired by the work @xekon did in #127.

See: https://fontawesome.com/how-to-use/on-the-web/advanced/svg-javascript-core
See: https://github.com/alanorth/hugo-theme-bootstrap4-blog/pull/127
 2020-01-27 18:17:35 +02:00
Alan Orth
06113fcd44
CHANGELOG.md: Add note about Font Awesome 5 2020-01-25 21:24:50 +02:00
Alan Orth
769c25e2c2
Regenerate static assets 2020-01-25 21:22:31 +02:00
Alan Orth
4c5ce590f2
Update to Font Awesome 5 
Nothing really new as far as how we're using Font Awesome, but it is
good to keep up with the times and the tooling. Users that have used
custom fonts in their content or layouts will need to update their
icon prefixes from "fa" to "fas" or "fab" depending on which font
their icon comes from.

See: https://fontawesome.com/how-to-use/on-the-web/setup/upgrading-from-version-4
 2020-01-25 21:20:44 +02:00
Alan Orth
9b35f3b1dc
Regenerate static assets 2020-01-25 16:42:52 +02:00
Alan Orth
ba6358ca48
source/scss/font-awesome.scss: Remove Google+ icon 2020-01-25 16:42:08 +02:00
Alan Orth
77e240280a
CHANGELOG.md: Add note about Google Plus 2020-01-25 16:07:18 +02:00
Alan Orth
32af219491
layouts: Remove a few more references to GooglePlus 
The sharing icons were removed in 2019, but these remained.
 2020-01-25 16:05:51 +02:00