1
0
mirror of https://github.com/alanorth/hugo-theme-bootstrap4-blog.git synced 2024-12-23 02:42:21 +01:00
Commit Graph

598 Commits

Author SHA1 Message Date
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
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
ce89342827
exampleSite/config.toml: Show how to override date format 2020-03-22 15:28:33 +02:00
a2ac9fe29e
CHANGELOG.md: Update cookieconsent to 3.1.1 2020-03-22 15:10:23 +02:00
77e05f010e
Regenerate static asssets 2020-03-22 15:09:46 +02:00
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
9bbfab2f1b
Version 1.4.2 2020-03-22 11:17:27 +02:00
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
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
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
9676a9736b
CHANGELOG.md: Add note about fix for structured data 2020-03-19 15:27:51 +02:00
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
780444bfb0
README.md: Add note about Farsi 2020-03-16 11:57:37 +02:00
58d01baba6
CHANGELOG.md: Add note about updated dependencies 2020-03-16 09:49:32 +02:00
9fb0baa0a5
Regenerate static assets 2020-03-16 09:47:25 +02:00
550b5c066d
Run npm update
Brings new versions of rtlcss, webpack, and fontawesome.
2020-03-16 09:46:39 +02:00
3be21cba1d
CHANGELOG.md: Adjust headings 2020-01-28 11:06:03 +02:00
ce3e6a933f
CHANGELOG.md: Release v1.4.0 2020-01-28 11:01:34 +02:00
22001d38ea
CHANGELOG.md: Update notes for unreleased version 2020-01-28 10:59:46 +02:00
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
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
06113fcd44
CHANGELOG.md: Add note about Font Awesome 5 2020-01-25 21:24:50 +02:00
769c25e2c2
Regenerate static assets 2020-01-25 21:22:31 +02:00
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
9b35f3b1dc
Regenerate static assets 2020-01-25 16:42:52 +02:00
ba6358ca48
source/scss/font-awesome.scss: Remove Google+ icon 2020-01-25 16:42:08 +02:00
77e240280a
CHANGELOG.md: Add note about Google Plus 2020-01-25 16:07:18 +02:00
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
1fdd332862
.build.yml: Use Node.js v12 2020-01-23 20:16:15 +02:00
a5c50f69c2
theme.toml: Increase minimum Hugo version to 0.55
I think the new subresource integrity (SRI) stuff requires this.

See: https://gohugo.io/hugo-pipes/fingerprint/
2020-01-23 20:06:43 +02:00
d2ea109b47
README.md: Update comment about Node.js version
I've been using version 10 for a year or so. Looking at the Node.js
LTS schedule I see that version 12 is the latest LTS release so I
guess I'll start using that locally at least.

See: https://nodejs.org/en/about/releases/
2020-01-23 20:02:38 +02:00
xekon
5c3ffa7868 add summaryLength to example config, for faster learning and prototyping. 2020-01-23 20:01:05 +02:00
3047cfe356
Regenerate static assets 2020-01-23 19:55:37 +02:00
44861dfc36
source/scss/bootstrap.scss: Copy new version number
Otherwise it is very confusing because the generated style.css has
the wrong version number.
2020-01-23 19:55:15 +02:00
553af337c1
Run npm update
New minor versions of a few libraries.
2020-01-23 19:52:23 +02:00
63241061dd
layouts/_default/baseof.html: Fix comment about RTL
It's not just Arabic anymore now that I added Farsi strings!
2020-01-23 19:46:21 +02:00
13449f1519
package.json: Fix typo in build script
This builds the right-to-left version of the stylesheet (RTL).
2020-01-23 19:44:54 +02:00
341bff9891
CHANGELOG.md: Add note about subresource integrity 2020-01-23 19:43:32 +02:00
c41364cf19
Remove custom generatesri tooling
We are now using Hugo's built in SRI support, which is magical and
seamless, and also gives us the bonus of acting as a cache buster.
2020-01-23 19:40:49 +02:00
44e8c677a6
Use Hugo's built-in subresource integrity support
We can use Hugo's built-in SRI support instead of using our custom
SRI generator script (as cool as it was at the time). This is more
clean and gives us the added benefit of adding fingerprints to the
CSS and JS filenames, which acts as a cache buster.

See: https://gohugo.io/hugo-pipes/introduction/
See: https://github.com/alanorth/hugo-theme-bootstrap4-blog/issues/120
2020-01-23 19:34:21 +02:00
6e36b66fab
CHANGELOG.md: Add note about typo in README.md 2020-01-22 09:15:57 +02:00
90a04b31d4
Merge pull request #118 from xekon/fix-readme
Update README.md
2020-01-22 09:14:39 +02:00
xekon
70c475f490
Update README.md 2020-01-21 15:40:57 -08:00
1eb8d9009a
CHANGELOG.md: Bootstrap 4.4.1 2019-12-09 10:06:49 +02:00
293c7dff8c
Regenerate static assets 2019-12-09 09:37:24 +02:00
6117301edd
Bootstrap 4.4.1 2019-12-09 09:37:05 +02:00
f2dab16881
CHANGELOG.md: Add note about Farsi i18n strings 2019-12-04 09:57:36 +02:00
b2ea655810
layouts: Use right-to-left text for Farsi 2019-12-04 09:56:41 +02:00
df1ec1df21
i18n/fa.yaml: Add Farsi strings 2019-12-04 09:56:26 +02:00