Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add Microformats #3052

Merged
merged 8 commits into from
Jul 23, 2021
Merged

Add Microformats #3052

merged 8 commits into from
Jul 23, 2021

Conversation

dltj
Copy link
Sponsor Contributor

@dltj dltj commented Jul 10, 2021

This is an enhancement or feature.

Summary

Add microformats to markup

Context

See #3017

Copy link
Owner

@mmistakes mmistakes left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Overall happy with this PR. I'm not thrilled with adding duplicate markup in _layouts/single.html so if any of that can be removed or DRYed up I'd feel better about it.

But all of the class based markup added looks 💯.

{% if page.title %}<meta itemprop="headline" content="{{ page.title | markdownify | strip_html | strip_newlines | escape_once }}">{% endif %}
{% if page.excerpt %}<meta itemprop="description" content="{{ page.excerpt | markdownify | strip_html | strip_newlines | escape_once }}">{% endif %}
{% if page.date %}<meta itemprop="datePublished" content="{{ page.date | date_to_xmlschema }}">{% endif %}
{% if page.last_modified_at %}<meta itemprop="dateModified" content="{{ page.last_modified_at | date_to_xmlschema }}">{% endif %}

<ul class="hidden">
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is there a better way of applying microformats for this data? This is the sort of extraneous markup I wanted to avoid, especially since it's duplicating the published/modified datetimes from above along with the authorship that is already being applied the author sidebar.

I get all sorts of "code smells" from it not being DRY and having to hide it all via CSS.

Copy link
Sponsor Contributor Author

@dltj dltj Jul 11, 2021

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes—the repeated variables bother me, too. The driving cause for that is how microformats need the data to be the contents of the enclosing tag and Schema.org puts the data in attributes. Specifically:

microformats do not use link or meta elements within the content of the page and in some cases require particular elements to be used to encode information, such as using abbr to support the datetime-design-pattern as illustrated by the dtstart property in the example above. ("Mixing Syntaxes" heading at W3C's "Mixing HTML Data Formats" page)

I used existing tags where possible (the p-name class for the <h1> article title and the e-content class in the article <section> tag). The contents of the hidden <ul>, though, were the values from the Schema.org <meta> tags.

For a while, I was putting microformat markup in the _includes/page__meta.html, but separating the article microformat data across two template files felt like a worse compromise as compared to keeping all of the HTML data formats in close proximity in one template file.

Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

With all of the "hidden" list element items, which are actually required? Can we move forward with the other data you marked up that isn't hidden from view?

I'm still iffy on the duplicating all the author markup as it's in the sidebar with microformat markup now.

Can the published/modified dates be marked up in _includes/page_date.html instead? Neither of those are hidden and you wouldn't have to duplicate the markup then.

<ul class="hidden">
<li>These list items are microformat entries and are hidden from view.</li>
<li class="u-url">{{site.url}}{{page.url}}</li>
{% if site.author.name %}<li><a class="p-author h-card" href="{{ site.url }}"><img class="photo" src="{{ author.avatar | absolute_url }}">{{ site.author.name | markdownify | strip_html | strip_newlines | escape_once }}</a></li>{% endif %}
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Careful with your author variables. You start with site.author which will cause problems if someone has assigned an author to the post where it should override the "site" author.

You're also mixing in a {{ author }} variable to do the avatar. They probably should all be {{ author }}. Take a look at how the assign works in the author sidebar to see how I did it there.

A conditional is needed for author.avatar since we can't guarantee someone set an image and wouldn't want an empty <img>.

Either way I question if the author microformat markup is even needed here as you've added it to the sidebar already. Will it fail without it? Just trying to get a feel for how DRY this can be since I'm not really thrilled with all the duplicate markup.

Copy link
Sponsor Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Oh, wow... an excellent point about the mixing of author variables. I will fix that with an update to the branch.

Regarding the author microdata markup in two places. The markup in the sidebar is describing an h-card. In the microformats world, it seems like the site homepage should contain this markup to describe the controlling entity of the site. The author markup in the "_single.html" file covers the stated author of the article on the page for an h-entry. (And that is where I'm definitely misusing {{ site.author }}.

I'm not familiar with the mechanics of multi-author Jekyll blogs, but from what I can gather the site variables are appropriate for the sidebar (the "h-card" microformat covering the entire site) while the author variables are appropriate for the article itself (the "h-entry" microformat).

@dltj
Copy link
Sponsor Contributor Author

dltj commented Jul 11, 2021

Please see the updated commit to the PR. I'm using the assigned-author structure now. I found that it does not have an author "URL" defined in it, so I removed that from the markup rather than making the assumption that the blog root is the author's URL. The Microformats crowd would probably strongly prefer that to make explicit the connection between the article author and its "h-card" representation, but it is technically optional. I could also add an author URL to the sample _config.yml, but that seems like overkill for this specialized purpose.

@dltj dltj requested a review from mmistakes July 12, 2021 03:45
* Move dt-published to `page__date.html` and remove dt-updated
* Remove "author" and "summary"

Leaves "url" as a hidden element
<ul class="hidden">
<li>These list items are microformat entries and are hidden from view.</li>
<li class="u-url">{{ page.url | absolute_url }}</li>
</ul>
Copy link
Sponsor Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hmm—the specification is fuzzy ("No properties are explicitly required") and then goes on to say an "h-entry should have the following properties at a minimum for consumers:"

  • url
  • dt-published (timestamp)

In this latest commit, I moved dt-published to page__date.html as you suggested and removed dt-updated (the if..else markup in page__date.html doesn't distinguish between published and updated when it is rendered to the page). I also removed p-author and p-summary as they aren't in the required subset.

That leaves u-url. Interestingly, there is a {{ page.link}} in _layouts/single.html, but I can't find a condition where page.link would have a value (unless it is expected to come from the page front matter). Unfortunately, u-url is a required data element. Thoughts on how to handle this?

I'm still iffy on the duplicating all the author markup as it's in the sidebar with microformat markup now.

The duplication is necessary so the author information occurs within the enclosing h-entry markup, and the sidebar is outside that markup. But since it isn't required I just removed it.

Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The duplication is necessary so the author information occurs within the enclosing h-entry markup, and the sidebar is outside that markup. But since it isn't required I just removed it.

Now I’m remembering why I wasn’t keen on adding microformats years ago 🤣. It would be so much better if it leveraged other standards especially all this data is already in the head or other schema used in the SEO include.

The page.link variable stuff is for “link” posts so you can’t rely on it. https://mmistakes.github.io/minimal-mistakes/post%20formats/post-link/

Maybe the best path forward is add the bare minimum of microformats that doesn’t duplicate markup. Then let me noodle on future support.

The theme is showing it’s age and a lot of other features being requested could benefit from me doing a complete overhaul. Microformats could be lumped in with that…

Copy link
Sponsor Contributor Author

@dltj dltj Jul 16, 2021

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, I am disappointed that the IndieWeb folks aren't using something more structured like Schema.org, but I don't have any leverage to steer that community...and it seems like they have quite the organic mix of tool providers that are using microformats.

Are you okay with merging the pull request as it is now? The minimal parts of microformats for Card and Entry have been added to the existing theme markup with the exception of the hidden <ul> list with the one list item for the URL to the post. I could clean up the wording of the list item explaining the hidden list—say, "This list item holds the microformat entry for the link to this post, and it is hidden from view"—and make a final commit to this pull request, if you prefer.

If not, I'm happy maintaining my own fork of mmistakes to get the microformats functionality. (Which is using the organic-mix-of-tools to get Twitter and Facebook conversations onto the blog post entry.)

Copy link
Owner

@mmistakes mmistakes Jul 19, 2021

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The hidden content still gives me a bad feeling.
In fact was looking at the Microformats wiki and they even discourage it.

If some content doesn't fit into your visible design, then it's not worth microformatting it.

Microformats provide a mechanism for marking up visible content. Any mechanism for embedding invisible or hidden content risks being considered spam due to the fact that invisible (meta)data inevitably ends up being abused. Avoid invisible (meta)data. Publish visible data.

https://microformats.org/wiki/faq#Hidden_Content

Copy link
Sponsor Contributor Author

@dltj dltj Jul 22, 2021

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You're right: the Microformats wiki does discourage the use of hidden content. That said, I think having something in the markup that points to itself seems to be a pretty critical idea—especially if some machine process is going to extract the data out of the page to make use of somewhere else.

I went poking through the Schema-org markup for CreativeWork, and there is a property from the inherited Thing for URL—and that property isn't used in the mmistakes markup at the moment. Perhaps a permalink can be added to the footer of the article, and that can be marked up with both itemprop="url" (for Schema-org) and class="u-url" (for Microformats).

image

<p>
  <strong><i class="fas fa-fw fa-bullseye" aria-hidden="true"></i> Permalink:</strong> <span itemprop="url" class="u-url">https://dltj.org/article/dltj-with-webmention/</span>
</p>

If you like, I could wrap it in a Jekyll {% if %} block that checks for a feature flag that is set to "false" by default so the addition doesn't have a visible impact on existing sites.

Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What if instead of adding it to the footer metas... and adding yet another config toggle, you include the permalink in the h1 with the post title? I don't think it harms anything doing that.

<h1 id="page-title" class="page__title" itemprop="headline">
  <a href="{{ page.url | absolute_url }}" class="u-url">{{ page.title | markdownify | remove: "<p>" | remove: "</p>" }}</a>
</h1>

About the only change would be a visual one as the title is now styled like a link... which I don't see any issue with.

Screen Shot 2021-07-22 at 3 36 39 PM

The h1 tag now contains the Schema-org `url` itemprop and the
Microformats `url` class in an anchor tag.  The anchor tag is styled to
not look like a link.
@dltj
Copy link
Sponsor Contributor Author

dltj commented Jul 23, 2021

Yes, this looks good. I didn't like the styling of the <h1> tag as a link, so I overrode that in the SCSS to make it look as it did before.

How does this PR look to you now? I presume you will squash all of these commits into one merge to master, but if you rather I make a new PR with just one commit with all of the changes, I'm happy to do that.

Copy link
Owner

@mmistakes mmistakes left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the work on this PR. We're really close. Just the small Sass variable change and then replacing out the hidden author URL markup and this will be good to merge.

<div itemscope itemtype="https://schema.org/Person">
<div itemscope itemtype="https://schema.org/Person" class="h-card">

<a class="u-url hidden" rel="me" href="{{ '/' | relative_url }}">
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we remove this hidden markup since u-url is being applied to the author.home link.
If u-url is required and the thought was to add the hidden markup because there is no guarantee someone adds author.home to their config.

Perhaps we can do a similar thing to the post title. In this case make the author name a link... use author.home first fallback to the site's root URL if the home link hasn't been configured.

<h3 class="author__name" itemprop="name" class="p-name">{{ author.name }}</h3>
  <a class="u-url" rel="me" href="{{ author.home | default: '/' | relative_url }}">{{ author.name }}</a>
</h3>

@@ -72,6 +72,11 @@ body {
margin-top: 0;
line-height: 1;

a {
color: $dark-gray;
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Replace with $text-color variable so each of the skins can assign the correct text color to match. They're not all dark gray.

This also puts the same `{{ author.home | default: '/' | absolute_url }}`
construct on `author__avatar` to remove the Jekyll `author.home`
conditional.

Also addresses SCSS text color error.
@dltj
Copy link
Sponsor Contributor Author

dltj commented Jul 23, 2021

Ah, yes—moving that hidden markup into the author__name <h3> is a good pattern. Speaking of good patterns, I also applied the same {{ author.home | default: '/' | absolute_url }} construct to the author__avatar block immediately above this code to remove the {% if author.home %} conditional.

$text-color fixed too...that was a midnight mistake.

Copy link
Owner

@mmistakes mmistakes left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

All systems are go!

@mmistakes mmistakes merged commit 65e79f5 into mmistakes:master Jul 23, 2021
@dltj
Copy link
Sponsor Contributor Author

dltj commented Jul 23, 2021

Many thanks. I appreciate working with you on this.

friskgit pushed a commit to friskgit/minimal_website that referenced this pull request Aug 24, 2022
* Add rel=me to author profile links

* Add h-card Microformats markup

* Add h-entry microformat markup

* Fix missing anchor tag

* Fix h-entry microformat markup on single template

* Use minimal subset of Microformat elements

* Move dt-published to `page__date.html` and remove dt-updated
* Remove "author" and "summary"

Leaves "url" as a hidden element

* Add page link to h1 tag

The h1 tag now contains the Schema-org `url` itemprop and the
Microformats `url` class in an anchor tag.  The anchor tag is styled to
not look like a link.

* Put author 'u-url' on author__name h3

This also puts the same `{{ author.home | default: '/' | absolute_url }}`
construct on `author__avatar` to remove the Jekyll `author.home`
conditional.

Also addresses SCSS text color error.
joeroe added a commit to joeroe/joeroe.github.io that referenced this pull request Nov 11, 2022
infotexture added a commit to infotexture/minimal-mistakes that referenced this pull request Jan 23, 2023
This builds on the microformats enhancements contributed by @dltj in mmistakes#3052.

Adding `rel="me"` to footer links [enables web sign-in](https://indieweb.org/How_to_set_up_web_sign-in_on_your_own_domain) or [RelMeAuth](https://microformats.org/wiki/RelMeAuth), so you can use your domain to sign in to other sites.

In mmistakes#3052, the `rel="me"` attributes were added to the author profile, but that only appears in post sidebars, and web sign-in requires these profile links to be present on the home page.
kaitokikuchi pushed a commit to kaitokikuchi/kaitokikuchi.github.io that referenced this pull request Sep 4, 2023
* Add rel=me to author profile links

* Add h-card Microformats markup

* Add h-entry microformat markup

* Fix missing anchor tag

* Fix h-entry microformat markup on single template

* Use minimal subset of Microformat elements

* Move dt-published to `page__date.html` and remove dt-updated
* Remove "author" and "summary"

Leaves "url" as a hidden element

* Add page link to h1 tag

The h1 tag now contains the Schema-org `url` itemprop and the
Microformats `url` class in an anchor tag.  The anchor tag is styled to
not look like a link.

* Put author 'u-url' on author__name h3

This also puts the same `{{ author.home | default: '/' | absolute_url }}`
construct on `author__avatar` to remove the Jekyll `author.home`
conditional.

Also addresses SCSS text color error.
chukycheese pushed a commit to chukycheese/chukycheese.github.io that referenced this pull request Sep 18, 2023
* Add rel=me to author profile links

* Add h-card Microformats markup

* Add h-entry microformat markup

* Fix missing anchor tag

* Fix h-entry microformat markup on single template

* Use minimal subset of Microformat elements

* Move dt-published to `page__date.html` and remove dt-updated
* Remove "author" and "summary"

Leaves "url" as a hidden element

* Add page link to h1 tag

The h1 tag now contains the Schema-org `url` itemprop and the
Microformats `url` class in an anchor tag.  The anchor tag is styled to
not look like a link.

* Put author 'u-url' on author__name h3

This also puts the same `{{ author.home | default: '/' | absolute_url }}`
construct on `author__avatar` to remove the Jekyll `author.home`
conditional.

Also addresses SCSS text color error.
arshad115 added a commit to arshad115/arshad115.github.io that referenced this pull request Feb 19, 2024
* Change tab indent to space for consistency (mmistakes#2614)

* Fix link for author name (mmistakes#2575)

Missed from bcd6126

* Update CHANGELOG and history

* Update zh-cn (mmistakes#2576)

* Update zh-cn
* Update ui-text.yml

* Update CHANGELOG and history

* Use layout: none instead of null (mmistakes#2617)

* Use layout: none instead of null

* Update CHANGELOG and history

* Configure entries layout `list` or `grid` (mmistakes#2616)

* Configure entries layout `list` or `grid`

This allows to use grid layout on `page.entries_layout` on the home layout.

Included a break since when using grid the post images are too close to the horizontal line bellow `posts` text.

There's a entries div now surrounding the posts since the first row of the grid was having a slight padding on the left. The home now behaves like posts/categories/tags pages with grid but including the paginator.

For best results on desktop use `classes: wide` and `paginate: 4` on `_config.yml` (or multiples of 4 if you want more rows)

* Fix indent

* Archive subtitle leaves space on the bottom

* Now space is added through style

* Update CHANGELOG and history

* Include documentation for home page grid view

* Update 10-layouts.md

* Update UI text for zh-CN and zh-TW (mmistakes#2626)

* Update UI text for zh-CN and zh-TW

* Update CHANGELOG and history

Not touching last_modified_at this time - it's messy enough

* Update documentation for mmistakes#2621 (mmistakes#2624)

* Update documentation for mmistakes#2621

* Update CHANGELOG and history

* Update last_modified_at

* remove hidden posts from `/posts` (mmistakes#2625)

* Update CHANGELOG and history

* Show date of posts (mmistakes#2526)

* add date to read-time.html

* add option for show_date, dynamic icon style

* change read-time to post__meta

* cleanup post__metal.html

* cleanup post__meta include variables

* put date before read time

* remove space in include variable

* allow customisation of post__meta separator

* add some documentation

* oops fix typo derp

* add post date image

* change page meta separator customisation to CSS

* Update CHANGELOG and history

* Fix grammar

* Remove extra back ticks

* Release 4.20.0 💎

* Update remote_theme

* Fix grammar

* Fix grid `entries_layout` in home.html

* Release 4.20.1 💎

* Update remote_theme version

* Fix `entries_layout: grid`
Close mmistakes#2639

* Update CHANGELOG and history

* Change "fa" to "fas" for Font Awesome 5 (mmistakes#2649)

* main.js: fa -> fas for FA 5

* Update CHANGELOG and history

* added css changes, modified jquery.greedy-navigation and built the main.min.js again

* Removed duplicated CSS definitions (mmistakes#2666)

* Update CHANGELOG and history

* Added article:author used by Pinterest (mmistakes#2670)

* Update CHANGELOG and history

* Refactor page meta (mmistakes#2641)

* Rename include

* Add grid view test pages

* Rename `.post__meta-sep` and use CSS to add line break

* Improve collection grid archive

* Improve page grid archive

* Enable `grid`

* Don't show date icon if there is no `date` value

* Add blank line at EOF

* Add space

* Wrap date and reading time in named `span` elements

* Update CHANGELOG and history

* Bump copyright year

* Fix typo

Close mmistakes#2678

* Fix broken link in documentation

Close mmistakes#2677

* Release 4.20.2 💎

* Bump theme version

* Update allejo/jekyll-toc to v1.0.14

https://github.com/allejo/jekyll-toc/releases/tag/v1.0.14

* Fix dead link to "CI services" Jekyll (mmistakes#2692)

* Fix mmistakes#2635

* Update CHANGELOG and history

* Update README.md

* Update CONTRIBUTING.md

* Update stale.yml

* Fix closing tag of figures without captions in lists (mmistakes#2697)

When the figure helper is used in a list, which can be either ordered or
unordered, and no caption is specified, a line with text "</figure>"
will be shown below the figure on the rendered page.

This is because, if the '{% if include.caption %}' evaluates to false,
the lines between that 'if' statement and '{% endif %}' will be emptied,
not removed, so the block will be filled by empty lines.

HTML ignores redundant empty lines, but Markdown takes them seriously.
In addition, Markdown expects proper indentation of lines inside lists,
and the closing '</figure>' tag is not indented.  When combined, the
empty space and absence of indentation cause Markdown to process the
'</figure>' tag as a separate paragraph instead of an HTML tag, thus the
text for the tag is directly rendered on the page.

The fix for this issue is very simple: remove the empty space when
'include.caption' is false.  As described in
<https://shopify.github.io/liquid/basics/whitespace/>, this can be done
by adding hyphens to the 'if' and 'endif' tags.

* Update CHANGELOG and history

* Update CHANGELOG and history

* Norwegian translation (mmistakes#2702)

* Update CHANGELOG and history

* Update CHANGELOG and history

* Fix a small typo in documentation

* Update ui-text.yml for Vietnamese

* Added some translation for indonesian language

* Update indonesian translation

* Update CHANGELOG and history

* Update CHANGELOG and history

* Update jQuery to 3.5.1 (mmistakes#2713)

* Update jQuery to 3.5.1

Closes mmistakes#2712

* Build NodeJS

Run using `npm run build:js`

* Update CHANGELOG and history

* Release 4.21.0 💎

* Update `remote_theme` version

* Fix heading level

* Fix Font Awesome icon color in various skins

Close mmistakes#2724

* Update remote theme instructions

* jekyll-install-cache gem should be added to Gemfile

* Update CHANGELOG and history

* indonesian translation minor typo fix (mmistakes#2731)

* Update CHANGELOG and history

* Update 404.md (mmistakes#2737)

Removed Google Search script which no longer worked.
mmistakes#2597

* Update CHANGELOG and history

* Delete support.md

* Delete feature_request.md

* Update allejo/jekyll-toc to v1.1.0, skip headings without an ID (mmistakes#2752)

* Update allejo/jekyll-toc to v1.1.0, skip headings without an ID

https://github.com/allejo/jekyll-toc/releases/tag/v1.1.0

* Update CHANGELOG and history

* Add toc_sticky parameter's description (mmistakes#2741)

* Update CHANGELOG and history

* Fix typo

* Add hebrew translation (mmistakes#2760)

* Update CHANGELOG and history

* Add .webp to supported lightbox images (mmistakes#2788)

* Update CHANGELOG and history

* Remove google's fixurl.js from example (mmistakes#2789)

Unfortunately, it no longer exists.

* Update CHANGELOG and history

* Upgrade Lunrjs to 2.3.9 and switch to relative_url (mmistakes#2805)

* Update Lunr to 2.3.9

* Switch from absolute_url to relative_url

* Update CHANGELOG and history

* Allow custom gradient in page header overlays (mmistakes#2806)

* Allow custom gradient in page header overlays

* Update documentation

* Update CHANGELOG and history

* Add toggle option for RSS feed visibility (mmistakes#2787)

* add a "hide" value in config for atom

* Update footer to use param

* update header to use param

* Update docs to note configuration

* undo formatting

* use unless syntax

* unless syntax and indentation

* indentation

* Update CHANGELOG and history

* Use sort_natural instead of custom-logic (mmistakes#2756)

* Update CHANGELOG and history

* Allow custom sorting for collections (mmistakes#2723)

* Allow custom sorting for collections

* Update docs with custom sort of collections

* Refactoring

* Update CHANGELOG and history

* Release 4.22.0 💎

* Update

* Force rebuild of demo site

* Fix typos

* Remove G-stuff CSS (mmistakes#2852) (mmistakes#2855)

* Add alt attr to site logo in masthead (mmistakes#2824)

Co-authored-by: Michael Rose <mmistakes@users.noreply.github.com>

* Add note on TOC heading level issue (mmistakes#2902)

mmistakes#2892 (comment)

* Add Baidu site verfication (mmistakes#2830)

* Update CHANGELOG and history

* Remove all references to official public Staticman API instance. (mmistakes#2831)

* Updated Staticman docs

* remove any ref to official public instance in docs

* remove fallback instance for staticman v2

left staticman v1 untouched as I dunno how to deal with that

* Update CHANGELOG and history

* Datetime format (mmistakes#2844)

* datetime_format

* page__meta

* page__date

* page__date test

* update docs

* update docs

* Update CHANGELOG and history

* Color notices based on skin colors instead of fixed values (mmistakes#2887)

* Made notice Sass color mixing in based on $background-color and $text-color instead of hard-coded black and white values.

* Made some style adjustments to notices to improve readability.

Notice links are slightly darkened from the notice color, mostly because the gray-on-gray default notice links were very hard to read.  Rather than being $notice-color, they are `mix(#000, $notice-color, 10%)`.
The notice background mix and code-background mix can now be set with the SCSS variables $notice-background-mix and $code-notice-background-mix.
The default mix for background was adjusted to 80%, from 90%.
The default mix for code-background was adjusted to 90%, from 95%.
Skins that still didn't read well were adjusted individually.

* Adjusted sunrise $notice-background-mix to 75%

* Adjusted dark theme notice background mix colors back to the default

Co-authored-by: Tom Manner <tsmanner@us.ibm.com>

* Update CHANGELOG and history

* Document user custom element hooks (mmistakes#2815)

* Added documentation for including custom CSS on a site or page

* Removed non-configuration related content from 05-configuration.md and cleaned up some style in new sections of 16-stylesheets.md

* Moved small custom head documentation to a ProTip in _docs/06-overriding-theme-defaults.md

* Cleaned up some documentation, and added some example uses of custom head and footer.

* Replace double space with single

* Replace double spaces with single

Co-authored-by: Tom Manner <tsmanner@us.ibm.com>
Co-authored-by: Michael Rose <mmistakes@users.noreply.github.com>

* Update CHANGELOG and history

* Add Arabic Translation 📝

* Update onchange and uglify-js dependencies

* Fix typo

* Update

* Update 14-helpers.md (mmistakes#2940)

Fix missing backtick.

* Update CHANGELOG and history

* Fix Jekyll environment note in configuration documentation

Close mmistakes#2912

* Fix typo

Close mmistakes#2911

* Update stale action

* Update stale.yml

* FIx menu toggle

ref: mmistakes#2957

* Release 4.23.0 💎

* Update CHANGELOG and history

* Bump theme version

* Enable auto ads

* Update Google Adsense

* Update FUNDING.yml

* Update FUNDING.yml

* Update README.md

* Disable auto ads

* Update support buttons

* Update Adsense

* Add banner above related posts

* Update FUNDING.yml

* Update FUNDING.yml

* Fix broken image

Close mmistakes#3013

* feat: Search icon in masthead is a Font Awesome icon. (mmistakes#2774)

* feat: Allow search icon in masthead to be set to a Font Awesome icon.

* fix indentations

* Users wishing to avoid FontAwesome should override _includes/masthead.html

* Update CHANGELOG and history

* Loads font-awesome asynchronously (mmistakes#2967)

Loading font-awesome asynchronously allows to display the site faster. This change is advised by google pagespeed insights

* Update CHANGELOG and history

* Remove H2 as it is not important to site structure (mmistakes#3012)

This should not use a H2, as that is not an important headline, and thus a H2 here would probably hurt in page SEO.

* Update CHANGELOG and history

* Fix broken links in documentation

Close mmistakes#3004

* Remove `tabindex="-1"` from `input` elements in `search.html` layout

Make `input` elements accessible by keyboard.

Fixes mmistakes#2982

* Update README text for Gumshoejs license (mmistakes#3024)

* Update CHANGELOG and history

* Remove IE9 flexbox fallback (mmistakes#3042)

IE9 is absolutely, completely, totally dead. it's marketshare is less than 0.1%.
REF: https://caniuse.com/usage-table

Save some bytes in the HTML for all users by removing the fallback inline CSS.

* Update CHANGELOG and history

* Add giscus support (mmistakes#3022)

* Add script in same style as utterances

But adjusted for the various filed differences

* Add initial script

* Add default settings

* Update changelog

* Add feature to readme

* Add comments html

* add comment provider include

* update config in docs

* Add URL for additional reference

* docs for giscus comments

* Unrelated bugfix: add missing version separator

So that things match the "history" doc.

* add space

* update history doc

* update about doc

* add to test config yaml

* remove unnecessary / incorrect async attribute

* probably should pass the right config paths

* lowercase the repo name

* Update docs to address '1' and '0' for reactions_enabled

Figured I'd match the giscus format rather than convert a boolean to an int there.

* update two additional docs

* docs wording fix

* Release 4.24.0 💎

* Update version

* Remove site.url from first breadcrumb link (mmistakes#3051)

* Remove site.url from first breadcrumb link

Fixes mmistakes#3050

* Use relative_rul filter instead of site.baseurl

* Update CHANGELOG and history

* Fixed a grammar error in the german translation (mmistakes#3063)

* Update CHANGELOG and history

* fix: change heading tag of related posts section from `h4` to `h2` for SEO enhancement (mmistakes#3064)

* Update heading tag from `h4` to `h2`

* Update heading tag from `h4` to `h2`

* Update CHANGELOG and history

* Add instructions on how to unminify main.js for easier browser debugging (mmistakes#3055)

* Add instructions on how to unminify main.js for easier browser debugging

* Fixed Markdown style like sggested by @iBug

* Update CHANGELOG and history

* Make small grammar changes

* Update 01-quick-start-guide.md

* Add Microformats (mmistakes#3052)

* Add rel=me to author profile links

* Add h-card Microformats markup

* Add h-entry microformat markup

* Fix missing anchor tag

* Fix h-entry microformat markup on single template

* Use minimal subset of Microformat elements

* Move dt-published to `page__date.html` and remove dt-updated
* Remove "author" and "summary"

Leaves "url" as a hidden element

* Add page link to h1 tag

The h1 tag now contains the Schema-org `url` itemprop and the
Microformats `url` class in an anchor tag.  The anchor tag is styled to
not look like a link.

* Put author 'u-url' on author__name h3

This also puts the same `{{ author.home | default: '/' | absolute_url }}`
construct on `author__avatar` to remove the Jekyll `author.home`
conditional.

Also addresses SCSS text color error.

* Update CHANGELOG and history

* Enable toc sidebar scrolling (mmistakes#2874)

* Enable toc sidebar scrolling

* Refactor style rules

* Move style rules from 'navigation' to 'sidebar'

* Remove custom scrollbar styles

* Enable sticky toc on test post

* Update CHANGELOG and history

* Add margin around Google ads

* Add role to search (mmistakes#3086)

* Update CHANGELOG and history

* Added Danish translations (mmistakes#3095)

* Added Danish translations

* Fixed wrong commit.

* Update CHANGELOG and history

* Enable magnific popup on <a> tags only when it has <img> (mmistakes#3114)

* Update CHANGELOG and history

* Remove extra semi-colon

* Bump path-parse from 1.0.6 to 1.0.7

Bumps [path-parse](https://github.com/jbgutierrez/path-parse) from 1.0.6 to 1.0.7.
- [Release notes](https://github.com/jbgutierrez/path-parse/releases)
- [Commits](https://github.com/jbgutierrez/path-parse/commits/v1.0.7)

---
updated-dependencies:
- dependency-name: path-parse
  dependency-type: indirect
...

Signed-off-by: dependabot[bot] <support@github.com>

* Update CHANGELOG and history

* include video does not survive compress.html (mmistakes#3117)

* Update CHANGELOG and history

* Use GitHub issue templates (mmistakes#3133)

https://docs.github.com/en/communities/using-templates-to-encourage-useful-issues-and-pull-requests/configuring-issue-templates-for-your-repository

* Delete stale.yml

* Delete stale.yml

* Added optional label attribute (mmistakes#3128)

Added label attribute as per utterances optional label setting.

* Fix broken link & Add Baidu site verification (mmistakes#3139)

* Fix broken link
Link to Bing Webmaster Tools was broken.

* Fix broken link
Link to Open Graph debug tool was broken.

* Add Baidu site verification (mmistakes#2830)
Added `baidu_site_verification` to `_config.yml`

* Making verbiage consistent w/current _config.yml (mmistakes#3180)

The plugin in question comes by-default listed in _config.yml ; it's better to say that the user must _retain_ it as listed, not that the user needs to add it.

* Link clarifying adding plugins (mmistakes#3181)

The phrase "put them here!" doesn't sufficiently clarify what to do; I add link to the Jekyll documentation with the proper syntax.

* feat: Sort comments by date ascending (mmistakes#3184)

* Update Brazilian Portuguese translation (mmistakes#3204)

* Update Brazilian Portuguese translation

* Revert some translations to reduce friction

* Update CHANGELOG and history

* Update CHANGELOG and history

* Fix keybase class (mmistakes#3221)

* Fix keybase class

* Fix fas->fab

* Update CHANGELOG and history

* ✏ fix typo (mmistakes#3232)

* Update CHANGELOG and history

* Add missing comma (mmistakes#3318)

Co-authored-by: Yuchen Zhong <yuchen21@fb.com>

* Update CHANGELOG and history

* Automatically close invalid PRs using GitHub Actions (mmistakes#3313)

* Try auto-closing bad PRs

* Include empty PR body as well

* Add "Type: Invalid" label as well

* Update CHANGELOG and history

* Added sameAs (mmistakes#3087)

* Update CHANGELOG and history

* Use <a> color for blockquote.notice border (mmistakes#3140)

Close mmistakes#3068

* Update CHANGELOG and history

* Fix inline code style not applied to stylized text (mmistakes#3253)

* bug: inline code style not applied to stylized text

* Use double colons for pseudoelements

* Update CHANGELOG and history

* Update to Jquery 3.6.0 (mmistakes#3254)

* Update CHANGELOG and history

* fix typo about loading javascript in footer (mmistakes#3350)

* Update CHANGELOG and history

* add optinal lunr searching of pages (mmistakes#3352)

* Update CHANGELOG and history

* Exclude `main.scss` from Lunr search index

* Add Kiswahili translation (mmistakes#3489)

* Add Kiswahili translation

* Add Kiswahli to README

* Add Kiswahili to documentation

* Update

* Update attribution link (mmistakes#3553)

* Update CHANGELOG and history

* Update link to Font Awesome gallery (mmistakes#3599)

* Update CHANGELOG and history

* Make it possible to enable breadcrumbs per page (mmistakes#3096)

* Make it possible to disable breadcrumbs per page

* Update single.html

* Update single.html

* Update algolia-search-scripts.html (mmistakes#3102)

Fix issue mmistakes#3101

* Update CHANGELOG and history

* Replace with public YouTube video

Close mmistakes#3649

* Replace with public YouTube video embeds

* Update CHANGELOG and history

* Fix mmistakes#3096 enabling breadcrumb on all pages (mmistakes#3668)

* Remove IE9 upgrade notice (mmistakes#3666)

* Update CHANGELOG and history

* Fix mmistakes#3668 breaking "disable per-page when globally enabled" (mmistakes#3669)

* Fix mmistakes#3668 breaking "disable per-page when globally enabled"

* `default:` filter doesn't fit here

https://shopify.github.io/liquid/filters/default/

* Update CHANGELOG and history

* Improve PR close auto-comment message (mmistakes#3713)

* Improve auto-comment message

* Lock these PRs after closing

* add webrick

* whatever, line ending perhaps

* bug fix

---------

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: iBug ♦ <git@ibugone.com>
Co-authored-by: dianlujitao <dianlujitao@gmail.com>
Co-authored-by: Michael Rose <est.michael@gmail.com>
Co-authored-by: 谭九鼎 <109224573@qq.com>
Co-authored-by: Juan Ara <juan@juanylaura.es>
Co-authored-by: Michael Rose <mmistakes@users.noreply.github.com>
Co-authored-by: Andrey Kartashov <gorilych@gmail.com>
Co-authored-by: Lim Jing Heng <limjh16@gmail.com>
Co-authored-by: Miguel Belardinelli Prytoluk <prytolukster@gmail.com>
Co-authored-by: Johannes Ganzenmüller <jganzenmller@ebay.com>
Co-authored-by: Lars Olesen <lars@intraface.dk>
Co-authored-by: Leo <liaoyuan@gmail.com>
Co-authored-by: Kai A <kai.andresen@gmail.com>
Co-authored-by: Quan <8580008+quanengineering@users.noreply.github.com>
Co-authored-by: M. Akhyar Rahman H <akhyarrh@users.noreply.github.com>
Co-authored-by: Mitchell Skaggs <skaggsm333@gmail.com>
Co-authored-by: Susan Stevens <susan.stevens10@gmail.com>
Co-authored-by: Jip-Hop <Jip-Hop@live.nl>
Co-authored-by: gricn <gricn666@gmail.com>
Co-authored-by: Uri Brecher <uri.brecher@gmail.com>
Co-authored-by: PHOENiX <rlaphoenix@pm.me>
Co-authored-by: Sean Killeen <SeanKilleen@gmail.com>
Co-authored-by: Johannes Ganzenmüller <johannes.ganzenmueller@gmail.com>
Co-authored-by: Nicolas Elie <40382614+n-elie@users.noreply.github.com>
Co-authored-by: luweizheng <luweizheng36@hotmail.com>
Co-authored-by: Vincent Tam <VincentTam@users.noreply.github.com>
Co-authored-by: Tom Manner <zephrincochrane@gmail.com>
Co-authored-by: Tom Manner <tsmanner@us.ibm.com>
Co-authored-by: ShifraSec <48570596+MoElaSec@users.noreply.github.com>
Co-authored-by: David Lechner <david@lechnology.com>
Co-authored-by: Randall Wood <297232+rhwood@users.noreply.github.com>
Co-authored-by: Guillaume Gautreau <guillaume+github@ghusse.com>
Co-authored-by: Christian Oliff <christianoliff@pm.me>
Co-authored-by: Erik Westrup <erik.westrup@gmail.com>
Co-authored-by: Anton Brall <github@antonbrall.de>
Co-authored-by: Kulbhushan Chand <17742733+kulbhushanchand@users.noreply.github.com>
Co-authored-by: Peter Murray <jester@dltj.org>
Co-authored-by: Johnson <20457146+j3soon@users.noreply.github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Co-authored-by: John Scott <68079471+JohnScottUK@users.noreply.github.com>
Co-authored-by: Nathan Cho <ntcho13@gmail.com>
Co-authored-by: Jason Hemann <jason.hemann@gmail.com>
Co-authored-by: Daniel Schroeder <deadlydog@hotmail.com>
Co-authored-by: Georger Araújo <4930759+georgeraraujo@users.noreply.github.com>
Co-authored-by: Andrew McIntosh <amcintosh@users.noreply.github.com>
Co-authored-by: Sander Holvoet <holvoetsander@gmail.com>
Co-authored-by: Yuchen <yzhong52@users.noreply.github.com>
Co-authored-by: Yuchen Zhong <yuchen21@fb.com>
Co-authored-by: Nicholas Perry <ape.inago@gmail.com>
Co-authored-by: Benson Muite <bkmgit@users.noreply.github.com>
Co-authored-by: FavorMylikes <FavorMylikes@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants