v1.1.2
What's Changed
Fixed
- Doc entries are never responsive. A doc page is prose — like
foundations/overview— never a widget meant to be previewed at different breakpoints, but itsresponsiveYAML key still defaulted totruelike a component/page, so a doc got the viewport-preset/width toolbar unless every author remembered to setresponsive: falseby hand.ComponentParsernow forcesresponsive: falsefor everydocentry regardless of the YAML key — even an explicitresponsive: truein a doc's front-comment has no effect. Component/page kinds are unaffected (still defaulttrue, opt out withresponsive: false). - Consumer
iframe.body_classno longer bleeds onto doc pages. Same bug shape as the foundations fix in [1.1.0]:render-cell.twigapplied the consumer's site-wideiframe.body_classto<body>fordocrenders too — a consumer with a darkiframe.body_classbroke prose readability on a real doc page, reported after a consumer's doc rendered with the site's dark brand background. The global class is now skipped forkind == 'doc', mirroringfoundations. Deliberate difference fromfoundations: the per-entrybody_class(authored in the doc's own YAML front-comment) still applies — it's an explicit per-doc opt-in by the author, not a site-wide bleed, so it remains the doc's escape hatch.
Pull Requests
- #67 — fix(render): doc entries are never responsive and skip the consumer's global body_class
Full Changelog: v1.1.1...v1.1.2