JS-Naked sites Webring

[villepreux]

#enhancement #suggestion

Hello,

Have the JS-Naked Day website serve as a WebRing for websites that support being Naked "all the time" / "on demand" ?

Something classic like
https://js-naked-day.org/webring
https://js-naked-day.org/webring/previous
https://js-naked-day.org/webring/next
https://js-naked-day.org/webring/random

but that would invoke participating websites with ?js-naked url arg or #js-naked url hash to instruct them to get naked

Work hand in hand with https://css-naked-day.github.io for a common pattern ?

[macdonst]

@villepreux this is a great idea that I didn't have a chance to implement but will look at it soon.

[bkil]

And definitely make it work without JS of course! 😉

Adding an anchor means that JavaScript will have to condition itself based on its presence upon booting. Would a site still be eligible if the only script present on the page is a tiny inline one that checks the anchor and only loads further JavaScript files if it is missing something like js;dr nojs js-naked, etc? We could actually separate this question into another issue.

Otherwise each website owner would be required to run and maintain a dynamic backend (with at least SSI) that raises the bar a bit.

As a much lighter alternative, websites that are generated from human readable source during deployment by the CI/CD (such as SecuChart) could trivially ship two separate sites under different file names (or folders). E.g., /js/ vs. /css/. In this case, the nojs path might be the one to hook onto the webring.

We actually are thinking about such a refactor to generate and deploy 4 versions of the site:

• pretty CSS-only without JS: the present one
• HTML5, no CSS, no JS: individual information pages and a few pregenerated comparison tables, maybe basic widgets, but with topmost accessibility to humans and SEO. Could also probably generate gemini/gemtext from this.
• HTML0, JavaScript0, no CSS: would be fully interactive, bandwidth-efficient and offline-capable, but look less pretty