Repository navigation
Conversation
- Share an idea is the feed's composer in the brand's composer shape. It opens in place with the board, details, sign-in and submit, posts to the first board the visitor can post on, and goes to the posted idea. - Ideas vote by the feed's rules: the board's, and the viewer's. - Help search searches the help centre as you type, with Ask AI where the help centre offers it; its field takes the design's composer corners. - A board default that arrives after the composer mounts is taken while none is chosen.
…ards vote - A card surface is marked once, and the design CSS gives every one the design's card style: raised, as rows, filled or bordered. The feed, Home, the post's sidebar, the help centre, support, status and the welcome card now follow it, in place of three copies of the same classes. - Roadmap cards vote by the board's rules. The title's link covers the card and the vote sits above it, so neither is inside the other. - The parts list names the help search field, and the composer and vote where they are now drawn.
…lain Roadmap, Changelog, the help centre and Support open with a title in the design's headline type, where each had its own. A design sets them on the band as Home's headline is (layout.pageTitles) and can word each one (pages.titles), with an accent phrase like any headline; a page left unworded says what it usually does. On the design engine the help centre drops its own grid and glow for the design's. Appearance has a Page titles section, Quackback AI can set and word them, looks choose band or plain from the brand's site, and the preview shows a draft's titles as they are typed.
- A menu row wider than the screen fades at an edge with more beyond it, and scrolls the current page into view, where the end of the menu was cut off with no sign of more. - Roadmap columns share the page's width, where a few narrow columns left most of it empty. Their dots follow the design's status markers. - Tags take the status markers' style: tinted with their colour, in the brand's colours where the design maps statuses to them, and plain where statuses are in the ink. The changelog's categories read in the ink.
…band short - brand.fonts.display sets the page headlines in their own face, such as a condensed poster face, while section headings keep the heading font. Appearance offers it beside the heading and body fonts, Quackback AI can set it by name, and looks choose one when a brand's hero type differs. - A page title on the band keeps it short: no image beside or under the words, and less room around them. A page's own buttons there take the band's colours, so they read on it. - The roadmap's note on its height is a comment again, not page text.
…Support sits on a card - A post's title on its own page takes the design's page title size, held short of it for a long title. It is a part, post-heading, for a design's own CSS. - Signed out, Support's way in sits on a card in the design's card style, where it floated alone on the page.
…s headings step down one level From the second accessibility pass over the branded portals: - The status filters' counts were faded below the contrast the solver keeps; they now read in the pill's own colour. - An empty state titles itself at the level it is given. Support's sit under the page's title, so they are second-level headings.
…acing follow the design From the second brand critique: - A page's own buttons on the band inherit its ink, and centre with its words; the changelog's RSS button was dark on a dark band. - Every status and tag dot is drawn by one component that follows the design's status style: the feed's filters, similar posts and roadmap columns as well as badges. - Where page titles are on the band, a post opens on a strip of it with the way back to its board, where it opened on a plain page. - The roadmap's description is a line under its tabs, not a card around a few words; the help centre has room under a band title. - The parts contract covers parts drawn by routes as well as components.
Many brands keep their colour for the logo and links and fill their main buttons in black or their text colour. shape.fill sets primary buttons in the brand colour or the text colour; a button now names its variant, so the design colours primary buttons and leaves the others alone. Appearance has a switch for it, Quackback AI can set it, and looks choose it from a brand's own buttons. The status drawing in Appearance uses the semantic colours.
mortondev
force-pushed
the
feat/portal-design-v2-parity
branch
from
October 31, 2026 18:22
6e03773 to
f6e2582
Compare
Member
Author
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
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.
Stack created with GitHub Stacks CLI • Give Feedback 💬