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

Fixes and improvements. #1160

Merged
merged 13 commits into from Oct 14, 2016
Merged

Fixes and improvements. #1160

merged 13 commits into from Oct 14, 2016

Conversation

@ivan-nginx
Copy link
Collaborator

ivan-nginx commented Oct 9, 2016

CSS: add bs-callout notes style.

image

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.

ivan-nginx added 3 commits Oct 9, 2016
Update from original 5.1.0 (2016.10.09)
Possible, that's why was confilicts with #1079 in #1081 merge.
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 ivan-nginx changed the title Fix "word-wrap" invalid property value in "highlight.styl". Fixes and improvements. Oct 9, 2016
ivan-nginx added 10 commits Oct 10, 2016
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.
@iissnan iissnan merged commit 4a1f976 into iissnan:5.1.0 Oct 14, 2016
1 check passed
1 check passed
hound No violations found. Woof!
@iissnan
Copy link
Owner

iissnan commented Oct 14, 2016

Thanks. 👍

@iissnan iissnan added this to the v5.1.0 milestone Oct 19, 2016
@viniarck
Copy link

viniarck commented Nov 5, 2016

Thank you a million for this PR. Really appreciate it!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked issues

Successfully merging this pull request may close these issues.

None yet

3 participants
You can’t perform that action at this time.