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

Integrate HTML and CSS validator tags #152

Closed
silverhook opened this issue Jan 7, 2016 · 6 comments
Closed

Integrate HTML and CSS validator tags #152

silverhook opened this issue Jan 7, 2016 · 6 comments
Milestone

Comments

@silverhook
Copy link
Member

IMHO having valid HTML and CSS is important and I always try comply with it.

It’d be great if (maybe once we get compliant) we could have two small tags to notify the visitor (so 2000’s, I know!) that the website is HTML5 and CSS3 valid. Ideally with a link to the W3C validator.

The official W3C tags are just too chunky and ugly, but I think the Font Awesome variants of HTML5 and CSS3 e.g. in the footer would be more then enough. And these icons are already extensively used by Elegant, so they wouldn’t strike out too much.

@silverhook
Copy link
Member Author

I added the following code to the footer template:

<li class="elegant-w3c"><a href="//validator.w3.org/check?uri=referer"><i class="fa fa-html5"></i></a><a href="//jigsaw.w3.org/css-validator/validator?uri={{ SITEURL }}"><i class="fa fa-css3"></i></a></li>

It works fine and it looks pretty nice, even if I do say that myself 😼

validator button

If you click on the small HTML5 shield, the current page gets processed, if you click on the CSS3 shield, the main page’s CSS gets processed. I assume the CSS is the same for all the pages, so that limitation should be fine IMHO.

The only down side is that for some reason, now my blog generates 2-4 times as slow as before.

@silverhook
Copy link
Member Author

The slower generation seems to have been caused by the system at that time being busy with other processes. In the past days the generator seems to work fine.

@iranzo
Copy link
Member

iranzo commented Dec 3, 2018

Probably having a setting to show/hide this based on value? like
BACK_TO_THE_FUTURE=False ;-)

@silverhook
Copy link
Member Author

I’m still of the strong opinion that a website must pass W3C tests, but am OK making the validator tags show as an option – e.g. W3C_VALIDATOR_LINK=False

@iranzo
Copy link
Member

iranzo commented Dec 5, 2018

Years ago, I even tried to have them 'bobby' compliant: https://en.wikipedia.org/wiki/Bobby_(software)

In general, anything that ensures standard compliance plus accessibility compliance should be really good to have

@talha131 talha131 added this to the Elegant 3.0 milestone Jan 2, 2019
@talha131 talha131 modified the milestones: Roadmap, 2019 - Q3 Jun 17, 2019
@talha131
Copy link
Member

talha131 commented Jul 3, 2019

We have it in travis.

@talha131 talha131 closed this as completed Jul 3, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

3 participants