Summary
Create a polished BugDrop Lab page where developers can try, configure, style, and validate the widget before installing it on their own app.
Why
The current local E2E fixture looks a little like a setup lab, but it is test-oriented and not suitable for onboarding. A real lab would help developers build confidence in screenshot behavior, theme configuration, redaction markers, and generated script-tag settings.
Proposed Capabilities
- Preview widget theme, position, label, icon, color, radius, and optional fields
- Toggle screenshot modes: optional, required, auto
- Test full-page, selected-area, and selected-element capture flows
- Mark demo fields with
data-bugdrop-redact and preview the reporter UX
- Show generated
<script> tag config and markup snippets
- Provide realistic host-page examples rather than the raw E2E fixture
- Include light/dark/system theme previews
- Make it clear that redaction is best-effort visual masking for developer-marked elements, not automatic secret detection
Acceptance Ideas
- A developer can configure the widget visually and copy a valid script tag
- A developer can mark a demo field private and see how redaction appears in the screenshot flow
- The lab is separate from
/test/ E2E fixtures
- The page is documented as a setup/onboarding tool, not a production privacy guarantee
Summary
Create a polished BugDrop Lab page where developers can try, configure, style, and validate the widget before installing it on their own app.
Why
The current local E2E fixture looks a little like a setup lab, but it is test-oriented and not suitable for onboarding. A real lab would help developers build confidence in screenshot behavior, theme configuration, redaction markers, and generated script-tag settings.
Proposed Capabilities
data-bugdrop-redactand preview the reporter UX<script>tag config and markup snippetsAcceptance Ideas
/test/E2E fixtures