Parses colour, font, and type-scale values out of a standalone HTML
mockup (a self-contained page, as design tools export) and writes a draft
format.yml, seeded from an existing style for every token the mockup
cannot answer.
Arguments
- html
Path to the exported HTML file.
- id
New style id.
- from
Existing style to seed unresolved tokens from. Default
"minimal".- path
Destination directory (a style bundle folder is created inside, as in
designer_new_style()).- label
Human-readable style label. Defaults to
id.
Details
This produces a starting point, not a finished style. Tokens with no CSS
analogue – above all title.layout, the print-page architecture; also
page.columns, page.margin, page.twoside, header_footer.*,
and heading/table rule and role choices – are
left at the seed style's value and named in the printed report. Set those
by hand, informed by looking at the design itself.
They are print-page architecture with no analogue in a screen layout, so
they are never guessed; designer_tokens() lists the vocabulary to choose
from.
Run designer_validate_style() on the result before rendering with it –
an extracted colour, font, or scale can still be malformed or reference a
font family that is not bundled and needs to be declared and shipped
under assets/fonts/.