c23c74f4 - Render the handbook insider section single-column - #889
Merged
Conversation
The two blocks of section 79 inherited the standard cols-2 grid, which squeezes the three-image walkthrough of the explainer block into a half- width column and stacks its images vertically. The base .tests class is already a single-column grid, so the explainer runs full width with the images side by side and the screenshot catalog entry follows below.
Four existing single-column sections signal the deliberate layout via the CSS-less cols-1 marker; use the same convention here instead of the bare base class.
Contributor
Author
|
Two review passes (conformance + logic each). Pass 1 came back clean and verified the CSS effect numerically (full content width comfortably fits the three-image walkthrough that the half-width column used to stack); the only note — four existing single-column sections mark the layout with the CSS-less cols-1 marker class — was adopted in the second commit, and pass 2 confirmed the final state clean on both dimensions. |
TaprootFreak
marked this pull request as ready for review
August 3, 2026 21:55
TaprootFreak
added a commit
that referenced
this pull request
Aug 4, 2026
…od deploys (#892) ## Summary Two handbook changes following up on #885/#889: ### Walkthrough layout (user feedback on the live page) The three images of the insider-unlock explainer rendered neither cleanly side by side nor stacked: the flex items are caption-driven wrapper divs, so two images filled the row and the third wrapped below. The block now shows the **instructions first**, then the three images in an equal-thirds grid with captions wrapping under their image; below 700px the walkthrough stacks as full-width rows (matching the page's existing narrow-viewport behaviour, verified against a neighbouring section). Desktop and mobile renders were verified in a local browser before pushing; the final CSS-cascade cleanup is render-identical (byte-equal screenshots). ### Deploys: staging → production, DEV retired Every push to `staging` now deploys directly to handbook.realunit.app (`:latest`, PRD secrets). The `deploy-dev` job, the `develop` trigger and the `:beta` tag are removed, and the `paths:` filter is dropped deliberately: every staging merge ships, which also re-stages the api-/web-sourced handbook content the filter could never observe. All prose that described the old staging→DEV/develop→PRD split (workflow comments, both READMEs, three spots inside the handbook page itself) now describes the single production lane, and the build-check comments state precisely what that check gates (screenshot-assembly, store-listing sync, legal-sync, image build + container smoke) versus what only the deploy run exercises (SSH/secrets/rollout). The retired dev-handbook instance keeps serving its last state until it is decommissioned on the infrastructure side (container + DNS) — intentionally out of scope for this repo. The four `DEPLOY_DEV_*` repo secrets become unreferenced with this PR and can be deleted afterwards. ## Erratum Commit `b571848f` references issue #893 in its message; the intended reference is **#894** (pre-existing: the build check's asset smoke accepts 401 as existence proof, which the auth gate makes meaningless — found during the review passes here, tracked separately). Amending a pushed commit is out per repo policy, hence this note.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Follow-up to #885: section 79 (insider unlock explainer) inherited the standard
cols-2test grid, which squeezes the three-image walkthrough into a half-width column — the images stack vertically and the card grows very tall (see the deployed page). Switching the section to the base.testsclass (an existing single-column grid) lets the explainer run full width with its three images side by side, and the269-dashboard-insider-unlockedcatalog entry follows below.One attribute change plus an HTML comment explaining the deliberate deviation from the otherwise uniform
cols-2sections.