Audit HTML structure with W3C validator

[palewire]

I suspect the page is in pretty good shape, but running our HTML through https://validator.w3.org/ would be a good way identify any minor bugs in our layout.

[sunnyjain15699]

Hi! Would like to help you out in this issue. Show me the light.

[palewire]

You've been assigned the ticket. I think a good first step would be to go the w3c validator linked above and run the jupyter homepage through it. You could either start the patch whatever bugs you find there yourself, or post screenshots of the results here to log what's needed.

[sunnyjain15699]

@palewire I have a query which is , I need to check those pages that are build in the _site folder that got created after the build has been processed.

[sunnyjain15699]

This is the link where you can see the result, also I have the setup in my local as well @palewire : https://validator.w3.org/nu/?showsource=yes&showoutline=yes&showimagereport=yes&doc=https%3A%2F%2Fjupyter.org%2F

You can find the attach png here :

[sunnyjain15699]

You can check the PDF from here as well, it includes :
W3Validator including images, source .pdf

[palewire]

@sunnyjain15699, that's great! Thank you. There are some simple, clear things to fix in there if you want to try to take any of them on.

[sunnyjain15699]

Would love to take all of them. Are you going to create more issues officially from the one we identified w3c validator ? @palewire

[palewire]

I hadn't thought it thru. If you want to make the tickets, or just start putting in pull requests, I'd be fine with that. Let me know how I can help.

[krassowski]

I think the ultimate goal should be to have a GitHub Action which verifies HTML integrity continuously. I don't know of such action, but IMO we should keep it open until we have a task on CI ensuring that we do not get regressions.