Skip to content

feat(design): Quackback AI starts from a site's own wordmark, share image and every new choice - #868

Closed
mortondev wants to merge 2 commits into
feat/portal-design-v2-fontsfrom
feat/portal-design-v2-ai-foundations
Closed

mortondev wants to merge 2 commits into
feat/portal-design-v2-fontsfrom
feat/portal-design-v2-ai-foundations

Conversation

@mortondev

Copy link
Copy Markdown
Member

Starting from a website now brings its header logo: the element the page
marks as its logo, or its first link home, as the inline SVG or the
sharpest dark-on-light image inside it. An inline SVG takes the colours
its page gives it, from the site's CSS and its brand colour, so it does
not draw in black once copied out. It is stored as the design's wordmark
when it draws clearly wider than it is tall and holds nothing that runs,
with its own colours for status markers. The site's share image is
stored when it is a photo large enough for a band, and the model, which
sees it, decides whether it suits one. Files are named by their content,
and a look may place only the files stored for its start.

The three looks now choose every new setting: a second colour, support
and blend bands, the band's alignment and shape, a header on the band,
headline scale, tracking and case, an accent phrase, button shape,
status style, how the logo shows, and where Home's composer sits. The
design system says when each fits, and the edit tool's field guide
covers them, so a person can ask for any of them.


Stack created with GitHub Stacks CLI • Give Feedback 💬

@mortondev
mortondev added this pull request to stack #833 October 31, 2026 13:50
@mortondev
mortondev force-pushed the feat/portal-design-v2-ai-foundations branch from 99c9338 to fadd60d Compare October 31, 2026 14:32
…mage and every new choice

Starting from a website now brings its header logo: the element the page
marks as its logo, or its first link home, as the inline SVG or the
sharpest dark-on-light image inside it. An inline SVG takes the colours
its page gives it, from the site's CSS and its brand colour, so it does
not draw in black once copied out. It is stored as the design's wordmark
when it draws clearly wider than it is tall and holds nothing that runs,
with its own colours for status markers. The site's share image is
stored when it is a photo large enough for a band, and the model, which
sees it, decides whether it suits one. Files are named by their content,
and a look may place only the files stored for its start.

The three looks now choose every new setting: a second colour, support
and blend bands, the band's alignment and shape, a header on the band,
headline scale, tracking and case, an accent phrase, button shape,
status style, how the logo shows, and where Home's composer sits. The
design system says when each fits, and the edit tool's field guide
covers them, so a person can ask for any of them.
The check for an SVG file skipped its XML declaration and comments with a
regular expression that could backtrack on a run of comments. It now
steps past them in a loop, and a fetched SVG is stored from its markup's
start.
@mortondev

Copy link
Copy Markdown
Member Author

Condensed into #881. 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.

2 participants