mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Rito Rhymes" <rito@ritovision.com>
To: "Jonathan Corbet" <corbet@lwn.net>,
	"Rito Rhymes" <rito@ritovision.com>, <skhan@linuxfoundation.org>,
	<mchehab@kernel.org>
Cc: <linux-doc@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] docs: generate a static 404 page
Date: Mon, 30 Mar 2026 13:20:21 -0400	[thread overview]
Message-ID: <DHGAFEMKLESD.1ZBRRPMHZGG95@ritovision.com> (raw)
In-Reply-To: <87zf3pnwj7.fsf@trenco.lwn.net>

> 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?

I see I framed this far too generically. My intent was narrower.

I mentioned nginx because I had looked at the live
docs.kernel.org deployment and saw that it uses nginx. The patch
is intended primarily for the canonical live documentation site.

My reasoning is that, on a public site of this size, users will
still sometimes arrive at missing URLs through stale indexed
links, old bookmarks, mistyped paths, truncated URLs, or references
from external sites. In that case, a documentation-native 404
gives them a way back into search, site navigation, and the
documentation root instead of leaving them on a generic orphaned
server error page.

The translated 404 handling also follows a live-site purpose.
When a user lands on a missing page under translated documentation,
it is more useful to keep the recovery path within that same language
section than to send them back to the English root.

Rito

      reply	other threads:[~2026-03-30 17:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-29 15:20 Rito Rhymes
2026-03-29 16:54 ` Rito Rhymes
2026-03-29 18:04 ` Rito Rhymes
2026-03-30 15:53   ` Jonathan Corbet
2026-03-30 17:20     ` Rito Rhymes [this message]

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=DHGAFEMKLESD.1ZBRRPMHZGG95@ritovision.com \
    --to=rito@ritovision.com \
    --cc=corbet@lwn.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mchehab@kernel.org \
    --cc=skhan@linuxfoundation.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®