Re: [PATCH] docs: generate a static 404 page

[Jonathan Corbet <corbet@lwn.net>]

Rito Rhymes <rito@ritovision.com> writes:

> Broken links in static deployments currently fall back to a
> generic web server 404 page, which leaves users on an orphaned
> error page with no direct way to continue navigating the
> documentation site. Add a dedicated not-found page so deployments
> can serve a project-specific 404 instead.
>
> It keeps the normal documentation layout around the error state so
> users still have the search box, table of contents, footer links,
> and a clear route back to the documentation root. The penguin
> logo makes it less generic and adds character to what is
> otherwise a frustrating page to encounter.
>
> For translated documentation, generate 404 pages whose return
> link keeps users inside the current translation instead of always
> sending them back to the English root documentation.
>
> Actual 404 handling remains a web server concern.
>
> Signed-off-by: Rito Rhymes <rito@ritovision.com>
> Assisted-by: Codex:GPT-5.4

I don't think that this makes a lot of sense.

Who are your users, what is your use case?  Who do you think will do all
of the setup work to create a server with a custom 404 page, but can't
supply the page itself?

This is the kernel documentation, not a web-site construction kit.

Please slow down and think about solving real problems.  There is So
Much Work that needs to be done with the kernel documentation, but none
of it has to do with this stuff.  And, in any case, the merge window is
approaching, so significant changes will not be accepted at this point
even if they otherwise make sense.

Thanks,

jon