Part of #206 (Phase 2). Depends on nothing.
Why
/web-interface is the twelve-tile gallery of the camera's own WebUI, built from config/webui_gallery.yml through WebuiGallery; tools/webui-gallery/run.sh photographs a camera from the same manifest, so the page and the pictures cannot drift. /get-started already shows its first four tiles inside the new browser-frame component (app/views/pages/get_started.html.erb:58-80). The full page still renders in the old container as a plain figure grid. /majestic-endpoints is a 28-line pointer saying the endpoint list moved into the camera's WebUI, kept for inbound links from Google, the wiki and forum posts, deliberately out of the navbar and footer since 3f0753c, and yet still listed in app/controllers/sitemaps_controller.rb:26.
What to change
/web-interface: content_for :fullwidth; the twelve tiles in a browser-frame grid, still fed by WebuiGallery.screens, still passing tile and 2560px original as a pair for data-zoom; captions and the scene credit kept. test/controllers/web_interface_test.rb (tile count, every URL through the pipeline, alt text, captions, credit) passes unchanged./majestic-endpoints: content_for :fullwidth, the same two buttons, the same three reasons; removed from SitemapsController::PAGES. test/controllers/majestic_endpoints_test.rb passes unchanged, including the assertion that the homepage does not link it.- Both move from
legacy_pages_test.rb to relaunch_pages_test.rb.
Done means
- Both pages render in three locales, full-bleed;
web_interface_test.rb and majestic_endpoints_test.rb green without edits.
tools/webui-gallery/run.sh still installs its shots where the page reads them (run it, or show the manifest is untouched)./majestic-endpoints is absent from /sitemap.xml.- Screenshots before any PR.
Part of #206 (Phase 2). Depends on nothing.
Why
/web-interfaceis the twelve-tile gallery of the camera's own WebUI, built fromconfig/webui_gallery.ymlthroughWebuiGallery;tools/webui-gallery/run.shphotographs a camera from the same manifest, so the page and the pictures cannot drift./get-startedalready shows its first four tiles inside the newbrowser-framecomponent (app/views/pages/get_started.html.erb:58-80). The full page still renders in the old container as a plain figure grid./majestic-endpointsis a 28-line pointer saying the endpoint list moved into the camera's WebUI, kept for inbound links from Google, the wiki and forum posts, deliberately out of the navbar and footer since 3f0753c, and yet still listed inapp/controllers/sitemaps_controller.rb:26.What to change
/web-interface:content_for :fullwidth; the twelve tiles in abrowser-framegrid, still fed byWebuiGallery.screens, still passing tile and 2560px original as a pair fordata-zoom; captions and the scene credit kept.test/controllers/web_interface_test.rb(tile count, every URL through the pipeline, alt text, captions, credit) passes unchanged./majestic-endpoints:content_for :fullwidth, the same two buttons, the same three reasons; removed fromSitemapsController::PAGES.test/controllers/majestic_endpoints_test.rbpasses unchanged, including the assertion that the homepage does not link it.legacy_pages_test.rbtorelaunch_pages_test.rb.Done means
web_interface_test.rbandmajestic_endpoints_test.rbgreen without edits.tools/webui-gallery/run.shstill installs its shots where the page reads them (run it, or show the manifest is untouched)./majestic-endpointsis absent from/sitemap.xml.