-
Notifications
You must be signed in to change notification settings - Fork 25.6k
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Fix schema.org dates to ISO-8601 #2339
Conversation
_includes/comment.html
Outdated
@@ -13,7 +13,7 @@ <h3 class="comment__author" itemprop="author" itemscope itemtype="https://schema | |||
<p class="comment__date"> | |||
{% if include.date %} | |||
{% if include.index %}<a href="#comment{{ include.index }}" itemprop="url">{% endif %} | |||
<time datetime="{{ include.date | date_to_xmlschema }}" itemprop="datePublished">{{ include.date | date: "%B %d, %Y at %I:%M %p" }}</time> | |||
<time datetime="{{ include.date | date_to_xmlschema }}" itemprop="datePublished">{{ include.date | date_to_xmlschema }}</time> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
<time>
is already using date_to_xmlschema
for the datetime
attribute. My understanding the time between <time></time>
is the human readable format and not used.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You're right ! I reverted it.
* Fix schema.org dates to ISO-8601 * Revert date_to_xmlschema in <time> tag
* Fix schema.org dates to ISO-8601 * Revert date_to_xmlschema in <time> tag
* Fix schema.org dates to ISO-8601 * Revert date_to_xmlschema in <time> tag
* Fix schema.org dates to ISO-8601 * Revert date_to_xmlschema in <time> tag
* Fix schema.org dates to ISO-8601 * Revert date_to_xmlschema in <time> tag
This is a bug fix.
Summary
It seems that schema.org's date data type should be ISO-8601. So I updated
datePublished
anddateModified
format todate_to_xmlschema
.