4 Commits

This Branch

This Branch

All Branches

Author	SHA1	Message	Date
ssmithxandClaude Sonnet 5	d403b5e3ca	Merge first real hardware report, remove Raspberry Pi placeholder ... Lenovo ThinkPad X250 report from issue #1 (submitted via the site form). Reconstructed cpu/archy_version from the issue body by hand — the submitted YAML had them glued together with no newline between ("...2.60GHz"1.8.10-alpha), which buildYaml() does not reproduce on these same field values in isolation (tested directly), so this looks like a Gitea draft-restore or browser-autofill artifact during actual submission rather than a bug in the form itself. Values used here are unambiguous either way. Left the ThinkPad T430 example in place; only removing the Pi one was requested. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>	2026-09-03 22:45:00 +00:00
ssmithxandClaude Sonnet 5	c8f6102cfd	Add a real submission form, bypassing the broken Gitea issue-template render ... Gitea 1.27.1 on this instance silently ignores the ?template= param for .github/ISSUE_TEMPLATE/hardware-report.yml — the structured fields never render, just a blank title/body editor (confirmed live: same URL that's supposed to load the form shows nothing). Rather than debug Gitea's YAML issue-forms support, site/report.html is a plain form matching the schema that builds a title + markdown body (with a ready-to-merge YAML block) and opens Gitea's issues/new with them pre-filled via query params, which does work on this instance (verified live). Verified the full round trip in a real browser: filled the form, submitted, confirmed the opened Gitea tab has the correct title and a body containing valid YAML matching every field. Did not actually click "Create Issue" — no reason to leave a test issue on the tracker. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>	2026-09-03 22:37:27 +00:00
ssmithx	f188fe562f	fix: correct repo links to ssmithx/ArchyHCL (not lfg2025 — no org repo-create access yet)	2026-09-03 22:29:10 +00:00
ssmithxandClaude Sonnet 5	a22a9c9826	Initial scaffold: ArchyHCL, a community hardware compatibility list for Archipelago ... Modeled on three researched precedents (see README): OpenWrt's Table of Hardware for the browsable sortable/filterable table UX, postmarketOS's working/community/testing tiers for the status field (collapsed to working/partial/broken here), and RaspiBlitz's scattered GitHub-issues approach as a negative example to avoid — hence structured YAML report files validated against a JSON Schema instead of free-text issue threads. - data/reports/*.yml + data/schema.json: one file per report, schema requires `issues` whenever status is partial/broken - scripts/build.py: validates every report and builds site/data.json, fails loudly on bad data (same idea as archy's own validate-app-manifest.sh) - site/: plain HTML/CSS/JS, no framework or build step, fetches data.json client-side — search, filter by status/form-factor, sortable columns, click a row for issues/notes detail - .github/ISSUE_TEMPLATE/hardware-report.yml: structured submission path for contributors who don't want to touch git directly - .gitea/workflows/ci.yml: runs the build/validate step on push and PRs Not yet deployed anywhere — see README's Deployment section. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>	2026-09-01 11:32:58 +00:00