Skip to content

feat(design): start from a logo or a screenshot - #844

Closed
mortondev wants to merge 3 commits into
feat/portal-design-v2-phase3-polishfrom
feat/portal-design-v2-phase3-attachments
Closed

mortondev wants to merge 3 commits into
feat/portal-design-v2-phase3-polishfrom
feat/portal-design-v2-phase3-attachments

Conversation

@mortondev

@mortondev mortondev commented Oct 31, 2026 •

Copy link
Copy Markdown
Member

The eleventh of the stack that builds a new design engine for the portal. Quackback AI can start a design from a logo or a screenshot, and the composer can attach one to any request. Behind the portalDesignV2 Labs switch.

Starting from an image

Ask AI's first run gains a fourth start next to a website, a few words and the presets: "Start from your logo or a screenshot". The browser reads the image's main colours, so the image itself never leaves it, and Quackback AI builds three looks from them. With "Also make it our logo", the image becomes the workspace logo through the usual upload; the conversation says when it could not be saved. The editor and the preview refresh once it is.

The composer has an attach button. An attached image's colours go with the request and show as swatches beside it.

Reading colours well

  • On a screenshot, the page and cards outnumber the brand colour, which often marks only a button that anti-aliasing splits into shades too rare to rank. The palette gathers vivid pixels by hue and always keeps the largest group, and Quackback AI is told which colour is likely the brand's.
  • A look whose page background reads as a colour keeps its preset's background, and Quackback AI is told the brand colour belongs on the accent and the band, never the page. A gold logo once produced a gold page.

Verification

  • On the local brand workspaces: Kiln started from its logo with "Also make it our logo", got three amber-led looks on quiet pages, kept its logo in the header and published; Bramble attached a screenshot of its own portal and got its coral back as the accent.
  • New tests, each red first: the palette ranks, merges, ignores transparency, keeps a thinly spread brand colour and finds the most vivid; the server takes a palette alone or with a request; the view starts from an image, makes it the logo and refreshes, and sends an attached image's colours; a vivid page background is refused.

Ask AI's first run gains a fourth start: a logo or a screenshot. The
browser reads the image's main colours, so the image itself never leaves
it, and Quackback AI builds three looks from them. With "Also make it our
logo", the image becomes the workspace logo through the usual upload, and
the conversation says when that cannot be saved.

The composer can attach an image to any request; its colours go with the
request and show as swatches beside it.
On a screenshot the page and cards outnumber the brand colour on its
buttons, so the palette missed it and Quackback AI chose a dull accent. The
palette now keeps the most vivid colour with a real share of the image, and
Quackback AI is told which colour that is. A logo attached in Appearance
refreshes the editor and the preview once it is saved.
A look from a gold logo painted the whole page gold. A look's page
background is now kept only when it reads as a neutral, else it keeps its
preset's, and Quackback AI is told the brand colour belongs on the accent
and the band.

On a screenshot the brand colour often marks only a button, split by
anti-aliasing into shades too rare to rank. The palette now gathers vivid
pixels by hue and keeps the largest group, read from a larger sample.
@mortondev
mortondev added this pull request to stack #833 October 31, 2026 00:00
@mortondev mortondev changed the title feat/portal design v2 phase3 attachments feat(design): start from a logo or a screenshot Oct 31, 2026
@mortondev

Copy link
Copy Markdown
Member Author

Condensed into #878. The stack is now five PRs, #878 to #882; this branch is kept as it was.

@mortondev mortondev closed this Nov 1, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant