We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
This wouldn't be a high priority one. But good to have, so that our pages are markup compliant.
http://validator.w3.org/check?uri=thelakshyafoundation.org
The text was updated successfully, but these errors were encountered:
Though this is a good-to-have thing, we must ensure we write compliant markup in all future checkins.
For existing code, I plan to do it in two steps:
Sorry, something went wrong.
good. probably we should have a check while commiting code, to catch markup errors.
saich
No branches or pull requests
This wouldn't be a high priority one.
But good to have, so that our pages are markup compliant.
http://validator.w3.org/check?uri=thelakshyafoundation.org
The text was updated successfully, but these errors were encountered: