Informed by Google Lighthouse insights.
The demo of the light Academic template now achieves 100% Accessibility, 100% Best Practices, and 100% SEO scores.
Hero image can now be moved from the media library to the widget page folder, e.g. `home/`, to become responsively sized.
Scope: the built-in search engine.
Provides one consistent interface for searching and thus surfacing common search queries to the user and in future typeahead.
Also, display the search keyboard shortcut and improve accessibility in Book TOC menu.
The set of conditions that can cause a flicker in this case are `day_night: true` (allow visitor to change theme mode) with a dark theme (`light: false`) and a user device which prefers dark themes.
Fix#2080
Common queries can be added to `data/search_queries.yaml` (experimental feature).
Refactor Wowchemy keyboard shortcut parser.
Fix JS/CSS assets being minified/fingerprinted in dev env.
Close#2060
Adds support for breadcrumb navigation on Book pages.
Consider this feature experimental for now as it may still change. Add the following to bottom of `params.toml` to use:
```
[breadcrumb]
page_types = {book = true}
```
Future work: prefix link title with page icon when set in order to be consistent with Book menu links (https://github.com/wowchemy/wowchemy-hugo-modules/pull/2009#discussion_r549530364)
Informed by user demand to support all event types rather than just talks.
Brings consistency to further align Academic and Research Group templates.
BREAKING CHANGE:
Rename `talk` folder to `event`
Remove `type` set to `talk` in any event front matter (if applicable)
To keep existing `/talk/` URLs, set the following in `config.toml`:
```
[permalinks]
events = "/talk/:slug/"
```
To use, add label and display options to superuser's `social` links:
```
social:
- icon: twitter
icon_pack: fab
link: https://twitter.com/<USERNAME>
label: Follow me on Twitter
display:
header: true
```
A recent refactor caused Mermaid and HLJS themes to not always be applied correctly, for example with theme pack default of light mode but user chosen Dark mode.
Toggle lists have now been standardized in HTML. Functions just like the toggle lists on Github.
Also now supports Markdown in title and works better with longer titles (unlike the previous button based component).
For sites using the `.js-github-release` feature to get the latest release of their project, prevent sending request to GitHub everytime Hugo Server reloads pages.
When sharing the page of an author profile (/author/author-name), the avatar image was no longer shown as the sharing image.
Hugo team made a breaking change in recent Hugo versions to rename the page `.Kind` to `term` instead of `taxonomy` in this case so the statement was no longer triggered.
Fix#1987
Mermaid and Plotly need to have their max-width constrained or they can overflow page width as they set their own fixed max-width in pixels, which can be wider than the page.
One workaround is to set `grid-template-columns` to `100%`. Another is to set a responsive fixed max-width on their parent elements or article-container.
Fix 1c05374
Hugo allows two ways to set a production environment.
The HUGO_ENV approach used by Netlify was working fine, but in case of running `hugo server -e production`, the CSS file wasn't fingerprinted.
Previously, in case of a site with multiple books in a folder, all books shared the same side bar menu listing ALL books and their pages.
List of books (aka book of books) is naturally supported by creating an `_index.md` of `type: page` in the parent folder which contains multiple book folders.
Also bump version to v5 Beta 1.
Previously email only shown if exists and the email form is disabled.
However, both Formspree and Netlify no longer use email address as a parameter, and received request to show email (if entered), in addition to email form, so visitors have the choice to use their usual email client to send a message.
Therefore, show the email address if it was entered.
In case of loading a page with a hash set and having multiple Portfolio widgets (Isotope instances) with images, scroll directly to the offset only once all Isotope instances have fully loaded their images and initialised.
Fixes issue with scrolling conflicts due to 600ms hash scroll on page load combined with 600m hash scroll on each Isotope widget loaded, whilst hash offset, if occurring after one or more Portfolio widgets, can be converging.
Replace JS approach for onload scroll to anchor with CSS scroll-padding-top, now that the CSS standard added support for scroll offsets.
Fix#1992
