Proper links, don't require JavaScript #12

New issue

Open

opened 2025-10-20 17:39:09 +02:00 by gahbla · 1 comment

gahbla commented

2025-10-20 17:39:09 +02:00

(Migrated from github.com)

I'd like to strongly suggest not to rely on JavaScript for navigation and to use proper <a href="…"> links instead. Currently, all the “links” on the website only work if JavaScript is enabled in the browser, otherwise nothing happens when clicking on them. This is a problem for the following reasons:

Not everyone has enabled JavaScript.
Screen readers may have problems with the navigation.
If there's a bug in one part of the JavaScript, it could impair the navigation code.
It's very likely bad for SEO.
The imprint (Impressum) must legally be available without JavaScript.

Also, all the links don't use proper paths (e.g. /calendar) but only HTML anchors (e.g. /#calendar). This makes it completely impossible to …

… use anchors for headings. For example, the URL https://en.wikipedia.org/wiki/HTML_element#Anchor will make your browser scroll down to the Anchor section of that Wikipedia article.
… link to specific sections of text on a page (that feature is called “scroll to text fragment”). For example, when opening the URL https://github.com/WICG/scroll-to-text-fragment#:~:text=To%20enable%20users%20to%20more%20quickly%20find%20the%20content%20they're%20interested%20in, your browser will automatically scroll down to the phrase To enable users to more quickly find the content they're interested in.

By the way, could the links perhaps be translated (e.g. /kalender instead of /calendar)? (Hugo allows this.)

I'd like to strongly suggest not to rely on JavaScript for navigation and to use [proper `<a href="…">` links](https://en.wikipedia.org/wiki/Hyperlink#HTML) instead. Currently, all the “links” on the website only work if JavaScript is enabled in the browser, otherwise nothing happens when clicking on them. This is a problem for the following reasons: - Not everyone has enabled JavaScript. - Screen readers may have problems with the navigation. - If there's a bug in one part of the JavaScript, it could impair the navigation code. - It's very likely bad for SEO. - The imprint (*Impressum*) [must legally be available without JavaScript](https://www.fachanwalt.de/magazin/impressum-recht/impressum-kontakt-angaben#:~:text=Klicks%20v%C3%B6llig%20ausreichend.-,Die%20Erreichbarkeit%20darf%20au%C3%9Ferdem%20nicht%20von%20bestimmten%20Scripten%20oder%20Plug%2DIns%20(z.B.%20JavaScript%2DPopups)%20abh%C3%A4ngen.,-Ebenso%20sollte%20die). Also, all the links don't use proper paths (e.g. `/calendar`) but only HTML anchors (e.g. `/#calendar`). This makes it completely **impossible** to … - … use anchors for headings. For example, the URL [`https://en.wikipedia.org/wiki/HTML_element#Anchor`](https://en.wikipedia.org/wiki/HTML_element#Anchor) will make your browser scroll down to the `Anchor` section of that Wikipedia article. - … link to specific sections of text on a page (that feature is called “[scroll to text fragment](https://github.com/WICG/scroll-to-text-fragment)”). For example, when opening the URL [`https://github.com/WICG/scroll-to-text-fragment#:~:text=To%20enable%20users%20to%20more%20quickly%20find%20the%20content%20they're%20interested%20in`](https://github.com/WICG/scroll-to-text-fragment#:~:text=To%20enable%20users%20to%20more%20quickly%20find%20the%20content%20they're%20interested%20in), your browser will automatically scroll down to the phrase `To enable users to more quickly find the content they're interested in`. By the way, could the links perhaps be [translated](https://gohugo.io/content-management/multilingual/) (e.g. `/kalender` instead of `/calendar`)? (Hugo allows this.)

👍 1

dokriseum commented

2026-02-25 16:09:23 +01:00

(Migrated from github.com)

Danke für die ganzen Tipps! Wir werden das Projekt nochmal ganz neu machen.

👍 1