docs: add widget warm neutral restyle spec + plan#110
Closed
docs: add widget warm neutral restyle spec + plan#110
Conversation
Brainstormed restyle of the BugDrop widget on the bugdrop-widget-test venue using existing data-* customization API. Goal: polish the marketplace product screenshots so the widget reads as a shipped indie SaaS product, not an engineering mockup. Implementation lands in mean-weasel/bugdrop-widget-test (no bugdrop source changes needed).
Step-by-step plan for applying the warm-neutral styling to the bugdrop-widget-test venue and re-shooting marketplace screenshots. Paired with the design spec added in the previous commit.
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
1 participant
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.
Summary
Adds the design spec and implementation plan for restyling the BugDrop widget on the
bugdrop-widget-testvenue. Pairs with mean-weasel/bugdrop-widget-test#67 which shipped the actualdata-*attribute changes.What's in this PR
docs/superpowers/specs/2026-04-14-widget-warm-neutral-restyle-design.md— design spec walking through the problem (marketplace screenshots showed default-styled widget with near-invisible input borders), the constraints (no bugdrop source changes, test repo only), the token map of exact hex values, and the screenshot reshoot proceduredocs/superpowers/plans/2026-04-14-widget-warm-neutral-restyle.md— step-by-step implementation plan covering clone → branch → edit HTML → verify → commit → push → PR → preview check → reshoot → mergeNo code changes. Pure documentation to preserve design context for future reshoots and similar restyle work.
Why this lands on main
Following the pattern of other spec/plan docs committed under
docs/superpowers/(e.g.d01604f docs: add design spec for screenshot threshold benchmark). Making the reasoning visible in main means future contributors (and future-me) can see:data-*attributes are wired up insrc/widget/index.tsbut not yet in the READMETest plan