The GitHub Pages site for the longbridge organization, served at
https://longbridge.github.io/.
Its main job is keeping the pre-rename GPUI Component documentation URLs alive.
The docs used to live at longbridge.github.io/gpui-component/. The repository
was renamed longbridge/gpui-component → longbridge/gpui-kit and the site
moved to https://gpui-kit.com, which left every indexed URL returning 404.
The old path cannot be fixed by recreating a gpui-component repository: GitHub
drops the longbridge/gpui-component → longbridge/gpui-kit rename redirect the
moment a repository claims that name again. The organization site is the way
around it — GitHub Pages serves longbridge.github.io/<path> from a project
repository of that name when one exists, and falls back to this repository when
none does. With gpui-component gone, that prefix lands here.
Every route on the old site exists on the new one, so the mapping is a prefix
strip: /gpui-component/docs/components/button → https://gpui-kit.com/docs/components/button/.
GitHub Pages cannot issue a real 301, so redirection happens in two layers:
gpui-component/**/index.html— one generated page per known route, carrying an instant<meta http-equiv="refresh">and a<link rel="canonical">so search engines consolidate the old URL onto the new one.paths.txtholds the 294 routes, taken from the last commit that built the site at/gpui-component/.404.html— a JavaScript catch-all for anything the generated set misses (old.htmlsuffixes, stale deep links). It gets visitors to the right page, but the response is still a404, so it carries no ranking signal. That is why the generated pages exist alongside it.
gpui-component/sitemap.xml lists the old URLs so search engines recrawl them
and pick up the redirects instead of waiting for the 404s to age out.
bun script/generate-redirects.tsEdit paths.txt to change the covered routes; everything under gpui-component/
except that file is generated and should not be edited by hand.