support-card-feature
Request a feature
New block, variant, or capability. Used by site teams asking the Rhea team to add something to the shared library.
true
true
card-gap-default
support-card-review
Architecture review
Kickoff for a new site, migration assessment, or a design review on something tricky. 60–90 min working session.
true
card-gap-default
support-card-issue
Report an issue
Bug in a block, broken authoring flow, performance regression, accessibility issue. Critical issues are triaged same-day.
true
card-gap-default
support-card-contact
Contact us
Slack channel, email, office hours. Use this when your question doesn't fit a form.
true
card-gap-default
support-process
What happens after you submit
- Acknowledgment within 1 business day. Every request gets a response — even if it's "we're investigating."
- Triage. Feature requests go to the Rhea backlog. Architecture reviews get scheduled within a week. Bug reports get triaged by severity.
- Updates. You'll hear back when the request status changes — accepted, scheduled, in progress, complete, or declined.
- Slack for follow-ups. Once a request is open, ongoing discussion happens in #rhea-eds, not via the form.
SLAs: same-day for critical issues, one business day for acknowledgment, two weeks for feature triage.
support-not-sure
Not sure which form?
- "I want a new block / variant" → Request a feature.
- "I'm starting a new site or planning a migration" → Architecture review.
- "Something is broken" → Report an issue.
- "I have a quick question" → Slack #rhea-eds or Contact.
When in doubt, contact us. We'll route it.
