Launch preview edition of the public Device Database website

[mkerstner]

Problem statement

Based on the work in #37 we aim to launch the preview edition of the Device Database website for public access and consumption.

This public website should then eventually replace the existing Grafana dashboard and enable everyone - including non Home Assistant users of course - to access the device data collected so far.

By definition it is limited to device data kindly submitted by the Home Assistant community. This is also why this preview edition of the public website will be limited in what data points to show. Going forward, contribution will play an
essential part in further fostering the Device Database - which is out of scope for this iteration.

Community signals

As summarized in OpenHomeFoundation/goals#13

Scope & Boundaries

In scope

• Launch of preview edition of the public Device Database website
• Including 3 main pages
  • Landing page As a user consulting the Device Database website I want to have a landing page as a starting point to start my search OHF-Device-Database/backlog-items#133
  • Browse page As a user consulting the Device Database website I want to browse for devices using a faceted search and filter options OHF-Device-Database/backlog-items#60
  • Device detail page As a user consulting the Device Database website I want to get information for a specific device OHF-Device-Database/backlog-items#7
• Search, filtering and pagination
• Categorization
• Infrastructure and monitoring is in place to cope with expected additional traffic

Not in scope

• Final branding - Instead keep visual baseline to adapt once available
• Account / Login
• Contribution via the website (remains for now via the Home Assistant community)
• Export
• Affiliate linking or other means to fund the Device Database to remain sustainable
• Multi-language support - English only for now

Foreseen solution

• We are going to use Claude Design as an experiment to work on the frontend part of the public website
• This approach should unblock us from a frontend development capacity on the one hand but also ideally foster collaboration on the preview iteratively generated

Risks & open questions

Risks
- Having sufficient frontend dev capacities to establish the foundation needed in order to further involve our community going forward on the development perspective

• Mitigated by going with a Claude Design experiment approach

Open questions

• Legal and branding delivery window - which is by definition kept out of scope for now

Appetite

Medium - 6-8 weeks

Execution issues

No response

Decision log

Date	Decision	Outcome

[mkerstner]

Opportunity for the upcoming roadmap cycle aiming for a MVP launch of the public website in July

@matthiasdebaat @djwmarcx @PhilipTrauner @stvncode @arturpragacz @marcelveldt In case you are missing something please comment / adjust.

Remainder roadmap cycle scope is defined as discussed here #37 which serves as the foundation for this opportunity.