You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Retargeted 2026-09-26. This issue was written against the Rails views. Since #160, #162, #164 and #165, every page it names is built by the static bundle (frontend/apps/site), and the Rails templates are only the rollback path. #287 deletes those templates along with Rails (#304). The port reproduced the old look on purpose, pixel for pixel, so the restyle still needs doing. The work now happens in the Astro components, and the Rails files named in the original text are not the target.
Why
/web-interface is the twelve-tile gallery of the camera's own WebUI. It is built from config/webui_gallery.yml, and tools/webui-gallery/run.sh photographs a camera from the same manifest, so the page and the pictures cannot drift. The page is components/pages/WebInterface.astro: WebuiTile tiles and a ZoomDialog, fed by lib/webui.ts through the JSON export of that manifest, inside Container.astro. /get-started already shows its first four tiles in the new design.
/majestic-endpoints (components/pages/MajesticEndpoints.astro) is a short pointer saying the endpoint list moved into the camera's WebUI. It is kept for inbound links from Google, the wiki and forum posts, and is deliberately absent from the navbar and footer, yet it is still listed in the sitemap (SitemapsController::PAGES today; the static build's own sitemap after #303).
What to change
/web-interface: full-bleed, with the twelve tiles in the browser-frame grid /get-started uses. Keep it fed by the manifest's export, and keep each tile paired with its 2560 px original for the zoom. Captions and the scene credit stay.
/majestic-endpoints: full-bleed, the same two buttons and the same three reasons. Take it out of the sitemap, in Rails now or in sitemap.xml moves into the static build #303 if that lands first.
Change nothing under app/views.
Done means
Both pages render in three locales, full-bleed, without Container.
tools/webui-gallery/run.sh still installs its shots where the page reads them: run it, or show that the manifest and the export are untouched.
/majestic-endpoints is absent from /sitemap.xml, and the home page still does not link to it.
Part of #206 (Phase 2). Depends on nothing.
Why
/web-interfaceis the twelve-tile gallery of the camera's own WebUI. It is built fromconfig/webui_gallery.yml, andtools/webui-gallery/run.shphotographs a camera from the same manifest, so the page and the pictures cannot drift. The page iscomponents/pages/WebInterface.astro:WebuiTiletiles and aZoomDialog, fed bylib/webui.tsthrough the JSON export of that manifest, insideContainer.astro./get-startedalready shows its first four tiles in the new design./majestic-endpoints(components/pages/MajesticEndpoints.astro) is a short pointer saying the endpoint list moved into the camera's WebUI. It is kept for inbound links from Google, the wiki and forum posts, and is deliberately absent from the navbar and footer, yet it is still listed in the sitemap (SitemapsController::PAGEStoday; the static build's own sitemap after #303).What to change
/web-interface: full-bleed, with the twelve tiles in the browser-frame grid/get-starteduses. Keep it fed by the manifest's export, and keep each tile paired with its 2560 px original for the zoom. Captions and the scene credit stay./majestic-endpoints: full-bleed, the same two buttons and the same three reasons. Take it out of the sitemap, in Rails now or in sitemap.xml moves into the static build #303 if that lands first.app/views.Done means
Container.tools/webui-gallery/run.shstill installs its shots where the page reads them: run it, or show that the manifest and the export are untouched./majestic-endpointsis absent from/sitemap.xml, and the home page still does not link to it.npm testpasses infrontend/.