ssmithx/ArchyHCL
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
9 Commits 1 Branch 0 Tags
main
Commit Graph
3 Commits
Author SHA1 Message Date
ssmithx 27e1e14ea9 Add Dell OptiPlex 7040 Micro report (RAID->AHCI + relocated-drive boot entry)
Deploy / deploy (push) Successful in 2s
Details
2026-09-05 21:53:26 +00:00
ssmithxandClaude Sonnet 5 d403b5e3ca Merge first real hardware report, remove Raspberry Pi placeholder
Build and validate / build (push) Successful in 11s
Details 
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 a22a9c9826 Initial scaffold: ArchyHCL, a community hardware compatibility list for Archipelago
Build and validate / build (push) Successful in 1m38s
Details 
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