From: Alyssa Ross <hi@alyssa.is>
To: "Johannes Süllner" <johannes.suellner@mailbox.org>
Cc: Demi Marie Obenour <demiobenour@gmail.com>,
Angel J <iamanaws@httpd.dev>,
devel@spectrum-os.org
Subject: Re: [PATCH www] impressum: fix broken relative paths in subdirectories
Date: Sun, 28 Dec 2025 22:34:55 +0100 [thread overview]
Message-ID: <87zf721e9s.fsf@alyssa.is> (raw)
In-Reply-To: <DF8T76LJZUN0.P1M4GRMM4PQZ@mailbox.org>
[-- Attachment #1: Type: text/plain, Size: 1762 bytes --]
Johannes Süllner <johannes.suellner@mailbox.org> writes:
> On Fri Dec 26, 2025 at 9:37 PM CET, Demi Marie Obenour wrote:
>> Nice catch! I wonder if automation can reduce the chance of similar
>> problems. Could a template engine be used to reduce repetition?
>> Or at least check that all of the internal links are valid?
>
> I wondered the same after finding these broken links recently (I just
> procrastinated sending a patch), and looked for tools to find broken
> links. I found a few, the one I liked most is lychee
> (https://github.com/lycheeverse/lychee).
>
> Using Nix, it can be run on the homepage repository as follows:
> nix-shell -p lychee --run 'lychee --root-dir $PWD .'
>
> Doing this, some broken external links can also be found.
> Some external links are being reported as broken erroneously for me,
> namely to gnu.org and doi.org.
> However, there are also two links which are broken:
> 1. On logo/index.html: https://hazelnot.xyz/
> 2. On motivation.html: https://docs.saltstack.com/en/latest/
>
> The website of Hazelnot seems to be offline since about June 2024, see
> https://web.archive.org/web/20240301000000*/https://hazelnot.xyz/
> The documentation of Saltstack moved to a new domain.
> Qubes moved their docs too, although they have redirects in place.
> I have a patch for this already which will follow in a minute.
>
> Regarding the broken internal links, I wonder if we would be better
> off using absolute links to avoid copy-paste errors in the future?
That would prevent navigating the website locally during development, so
I'd rather not. It probably does make sense to move to a static site
generator at some point though, especially if the website acquires more
content.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]
next prev parent reply other threads:[~2025-12-28 21:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-26 3:17 [PATCH www] impressum: fix broken relative paths in subdirectories Angel J
2025-12-26 20:37 ` Demi Marie Obenour
2025-12-27 7:09 ` Johannes Süllner
2025-12-28 21:34 ` Alyssa Ross [this message]
2025-12-28 21:33 ` Alyssa Ross
2026-02-02 13:29 ` Alyssa Ross
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87zf721e9s.fsf@alyssa.is \
--to=hi@alyssa.is \
--cc=demiobenour@gmail.com \
--cc=devel@spectrum-os.org \
--cc=iamanaws@httpd.dev \
--cc=johannes.suellner@mailbox.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://spectrum-os.org/git/crosvm
https://spectrum-os.org/git/doc
https://spectrum-os.org/git/mktuntap
https://spectrum-os.org/git/nixpkgs
https://spectrum-os.org/git/spectrum
https://spectrum-os.org/git/ucspi-vsock
https://spectrum-os.org/git/www
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).