Easy-to-manage touch screens
Free, open-source touch screens. Guided USB setup, a drag-and-drop editor and local control. Made for Home Assistant.
Garden OS Home: this week, where to next, what
Translation pending
LifestyleJavaScript · HTMLGitHub @DaveHomeAssistOnlineOwner unconfirmed
Have you tried it? One tap is enough. No sign-in needed.
No updates detected yet. GitHub releases will appear here.
Owners of public repositories under a personal GitHub account can sign in to verify ownership and manage the introduction themselves. No administrator approval is needed.
Sign in, generate a verification file, and commit it to this repository’s default branch within 30 minutes. Files on other branches or forks do not count. Then check the file below to manage the project without administrator approval. Keep the file to retain your access.
If needed, you will go to sign-in. After signing in, return here and press your chosen verification button again.
Run /nomorevibe verify in your project folder to verify ownership and manage the introduction yourself.
Verify in one minuteAsk about other verification options
Raised bed garden planning ecosystem with scoring engine and narrative game
Taken from the repository README
Loading the full README. The saved excerpt is shown below.
A local-first raised-bed planning and story system. Root tools run entirely in
the browser; Story Mode can also use an optional signed authority service while
retaining local offline persistence.
Most garden planners answer "where should I plant this?" with weak reasoning transparency.
Garden OS focuses on explainable decisions:
• sun fit
• support fit
• shade tolerance
• access fit
• seasonal fit
• structural bonus
• adjacency effects
The system also highlights the limiting factor so users can make high-leverage changes quickly.Read the full README ↗A local-first raised-bed planning and story system. Root tools run entirely in the browser; Story Mode can also use an optional signed authority service while retaining local offline persistence.
Most garden planners answer "where should I plant this?" with weak reasoning transparency.
Garden OS focuses on explainable decisions:
The system also highlights the limiting factor so users can make high-leverage changes quickly.
.gos.jsongos-schema.jsonindex.html in a modern browser.garden-painting.html for Beds and
garden-planner-v5.html for the seasonal Planner.The current root surfaces can run without install, build, or runtime services. That is a shipping mode, not a permanent architecture rule.
Why this score? breakdown..gos.json for backup or sharing.garden-os/
├── index.html # Canonical Home redirect
├── index-v5.html # Current product Home implementation
├── garden-painting.html # Active v5 Beds editor and experiments
├── garden-planner-v5.html # Active v5 seasonal planner
├── garden-doctor-v5.html # Active symptom triage
├── journal.html # Local-first garden journal
├── how-it-thinks-v5.html # Plain-English scoring walkthrough
├── garden-theme.js # Shared light/dark preference + visible toggle
├── garden-pwa.js # Shared service-worker registration
├── gos-experiments.js # Cross-bed experiment contract/store
├── garden-cage-build-guide.html # Cage construction guide
├── garden-cage-ops-guide.html # Operations and maintenance guide
├── scoring-map.html # Scoring architecture reference
├── scoring-visualizer.html # Scoring debugger
├── system-topology.html # Ecosystem topology map
├── brand-guide.html # Brand token and component reference
├── specs/ # Data schemas and reference JSON
├── docs/ # Design docs, audits, roadmaps
├── AGENTS.md # Agent instructions (issue tracker deprecated; see docs/UI_ISSUES_TABLE.html)
├── CLAUDE.md # Architecture constraints
└── README.md # This file
cd story-mode && npm ci
npx playwright install chromium
cd ..
node scripts/verify-all.mjs
node scripts/verify-all.mjs --live-only --live-url https://davehomeassist.github.io/garden-os/story-mode/
garden-league-simulator-v4.html, archived) neutral clicks inspect/select without mutating the grid.E toggles eraser and Escape returns to neutral inspect behavior.Escape.This project follows the shared naming conventions in 30-shared-resources/shared-standards/NAMING_CONVENTIONS.md.
MIT (project-level convention).