Fixes and improvements. #1160
Merged
Fixes and improvements. #1160
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Update from original 5.1.0 (2016.10.09)
1. When TOC has content, TOC is Active and enabled by default. 2. When TOC hasn't content, only Sidebar is show and enabled (like on Homepage). 3. Add `<!--noindex-->` for some search engines like Yandex, because this is dublicate for <Hx> tags.
ivan-nginx
changed the title
Add mainEntityOfPage. https://search.google.com/structured-data/testing-tool/
There is errors in https://validator.w3.org/nu/ if remove protocols from schema.org. No need to remove "http" from schema.org links. No matter on what protocol work website, all microformats View site GitHub.com as example: there is 301 moved permanently from 80 to 443 port, but all links on schemes have "http" protocol. Also, before remove "http" from schemes, my site work on forced HTTPS (like GitHub) and all tests on shemes was passed successfully.
There is errors in https://validator.w3.org/nu/ if remove protocols from schema.org. No need to remove "http" from schema.org links. No matter on what protocol work website, all microformats will read. View site GitHub.com as example: there is 301 moved permanently from 80 to 443 port, but all links on schemes have "http" protocol. Also, before remove "http" from schemes, my site work on forced HTTPS (like GitHub) and all tests on schemes was passed successfully.
There is errors in https://validator.w3.org/nu/ if remove protocols from schema.org. No need to remove "http" from schema.org links. No matter on what protocol work website, all microformats will read. View site GitHub.com as example: there is 301 moved permanently from 80 to 443 port, but all links on schemes have "http" protocol. Also, before remove "http" from schemes, my site work on forced HTTPS (like GitHub) and all tests on schemes was passed successfully.
There is errors in https://validator.w3.org/nu/ if remove protocols from schema.org. No need to remove "http" from schema.org links. No matter on what protocol work website, all microformats will read. View site GitHub.com as example: there is 301 moved permanently from 80 to 443 port, but all links on schemes have "http" protocol. Also, before remove "http" from schemes, my site work on forced HTTPS (like GitHub) and all tests on schemes was passed successfully.
|
Thanks. 👍 |
|
Thank you a million for this PR. Really appreciate it! |
habren
pushed a commit
to habren/hexo-theme-next
that referenced
this pull request
Apr 9, 2017
Fixes and improvements.
This was referenced May 26, 2017
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
CSS: add bs-callout notes style.
Usage
{% note class %}
Content (md partial supported)
{% endnote %}
Class: default, primary, success, info, warning, danger
Live Demo.
P.S. In live demo i change style on my own custom styles.