Generate structured data blocks for common local business pages without making students memorize schema.org.
Digital Presence · No backend. No login. Client data stays local.
Local Schema Forge is a polished, local-first open-source tool from Volta's open-source program. It helps Tech and marketing students improving local SEO turn real community work into structured evidence, client-safe handoffs, and mentor-reviewable release packets.
Volta principle: digital equity is economic equity. Every tool in this collection is designed so students can ship useful, accountable technology for small businesses, nonprofits, and community organizations that are usually priced out of high-quality digital transformation.
Structured data is high leverage but tedious, easy to get wrong, and rarely done for small businesses.
Local SEO implementation for first websites and rebuilds.
valid schema blocks deployed
flowchart TD
Need["Community or client need"] --> Intake["Volta discovery intake"]
Intake --> Evidence["Evidence capture"]
Evidence --> Workbench["Local Schema Forge Code Generator"]
Workbench --> Score["Presence readiness"]
Score --> Cert["release certification"]
Cert --> A1["JSON-LD block"]
Cert --> A2["HTML script tag"]
Cert --> A3["Schema validation checklist"]
Cert --> Student["Student portfolio proof"]
Cert --> Sponsor["Sponsor-ready impact proof"]
classDef volta fill:#111827,stroke:#60a5fa,color:#ffffff,stroke-width:2px;
classDef equity fill:#ecfdf5,stroke:#16a34a,color:#052e16,stroke-width:2px;
classDef proof fill:#fff7ed,stroke:#f97316,color:#431407,stroke-width:2px;
class Workbench,Cert volta;
class Need,Intake,Evidence equity;
class Student,Sponsor proof;
flowchart LR
subgraph Modules["First-class modules"]
M1["Business type selector"]
M2["JSON-LD generator"]
M3["Validation checklist"]
M4["Page placement guide"]
end
M1 --> Workbench
M2 --> Workbench
M3 --> Workbench
M4 --> Workbench
Workbench["Local-first workbench"] --> Exports["JSON · CSV · Markdown · Print"]
Exports --> Review["Owner + mentor review"]
Review --> Launch["Client handoff"]
classDef module fill:#eff6ff,stroke:#2563eb,color:#172554;
classDef app fill:#f8fafc,stroke:#0f172a,color:#0f172a,stroke-width:2px;
classDef launch fill:#f0fdf4,stroke:#22c55e,color:#052e16,stroke-width:2px;
class M1,M2,M3,M4 module;
class Workbench,Exports,Review app;
class Launch launch;
sequenceDiagram
participant S as Student pod
participant T as Local Schema Forge
participant M as Mentor
participant C as Client
S->>T: Capture public evidence
S->>T: Score the digital gap
T->>M: Export review packet
M->>S: QA notes and approval
S->>C: Client-safe handoff
C->>S: Outcome feedback
This repository is authored in TypeScript. The checked-in JavaScript files are compiled artifacts so the project can run directly on GitHub Pages without a build server.
- Source:
src/**/*.tsandtest/**/*.ts - Build:
npm run build - Runtime artifacts:
src/**/*.jsfor static hosting
| Area | What ships in this release |
|---|---|
| Domain workbench | A purpose-built code generator interface for generate structured data blocks for common local business pages without making students memorize schema.org. |
| Local-first runtime | Runs as a static web app with local autosave and no server dependency. |
| Certification flow | Release gates require status, owner, severity, and evidence before production handoff. |
| Exports | JSON release bundle, CSV operational table, Markdown certification report, print-ready handoff. |
| Integrity | Deterministic certification hash detects changed evidence. |
| Safety | Privacy notes, secret-safe markdown checks, wrong-product import rejection, client-safe defaults. |
| Accessibility | Skip links, keyboard-friendly controls, ARIA meter/list semantics, high-contrast focus support. |
| # | Module | Why it matters |
|---|---|---|
| 1 | Business type selector | Converts field work into repeatable, reviewable Volta delivery evidence. |
| 2 | JSON-LD generator | Converts field work into repeatable, reviewable Volta delivery evidence. |
| 3 | Validation checklist | Converts field work into repeatable, reviewable Volta delivery evidence. |
| 4 | Page placement guide | Converts field work into repeatable, reviewable Volta delivery evidence. |
| Gate | Acceptance signal |
|---|---|
| 1 | public evidence captured |
| 2 | owner handoff is plain-English |
| 3 | accessibility basics checked |
| 4 | local SEO output exported |
Full release quality gates
- All exports work offline
- Privacy and data handling documented
- No blocked critical gates
- Every certified claim has evidence
- Import rejects wrong product bundles
- Release hash is deterministic
- Client-safe markdown contains no secrets
- CSV contains every operational row
- Generated JSON must parse
- Required fields by type
- Opening hours format enforced
This project now includes a backend-grade engine because the workflow benefits from server-side validation, batch processing, or future API use.
| Runtime | Path | Purpose | Test command |
|---|---|---|---|
| Rust | backend/rust |
Deterministic release-gate scoring, fingerprints, high-performance validators. | npm run test:rust |
This repo is designed to be usable as a real OSS product, not just a static demo.
| Layer | Included |
|---|---|
| Reproducible build | package-lock.json, npm ci, TypeScript build artifacts |
| Local runtime | Static app via npm start |
| Container runtime | Dockerfile, docker-compose.yml, hardened Nginx config |
| Developer environment | .devcontainer/devcontainer.json |
| Operations | Makefile, .env.example, deployment docs, API docs |
| CI/CD | GitHub Actions CI, release artifact workflow, Dependabot |
| Backend | Rust deterministic validator API |
git clone https://github.com/volta-npo/local-schema-forge.git
cd 07-local-schema-forge
npm install
npm test
npm run test:backend
npm startThen open the local URL shown by Python, usually:
http://localhost:4173
No install step is required for the app itself. Tests use Node's built-in test runner.
This tool now includes a SaaS-style product workbench layer on top of the local-first release packet. The domain workspace models buyer personas, launch stages, commercial readiness, next-best actions, enriched CSV rows, a product backlog CSV, a client-facing launch brief, and a structured SaaS JSON packet. Product-specific rows, artifacts, checks, and sample data are expanded for the actual workflow in this repository instead of only generic release certification. The expanded commercial layer also includes product modules, reusable playbooks, unit-economics positioning, an operator runbook, a sales one-pager, and an implementation-plan CSV so the app can operate more like a standalone SaaS workbench than a static checklist.
This repository includes 31 automated tests covering core scoring, domain behavior, v1 release behavior, and release certification.
npm test
npm run verifyTest coverage includes:
- configuration weights and launch readiness
- product-specific domain sample data
- advanced SaaS module board, playbooks, economics, and commercial exports
- artifact generation and markdown exports
- v1 launch packet behavior
- release import/export round trips
- wrong-product import rejection
- deterministic integrity hashes
- blocked/critical gate prevention
- markdown safety checks
.
├── index.html # Static app shell
├── styles.css # Responsive Volta UI system
├── src/
│ ├── config.js # Product mission, rubric, and sample data
│ ├── domain.js # Domain-specific workbench definition
│ ├── domain-core.js # Domain calculations and artifacts
│ ├── v1*.js # v1 release layer
│ └── v3*.js # v3 release certification layer
├── test/ # 31 automated tests
├── docs/ # Operations, QA, release checklist
└── examples/ # Release bundle template
Volta works with students, nonprofits, and small businesses to make practical digital transformation accessible. These repositories are intentionally:
- small enough to understand in a student pod
- useful enough to run in a real community engagement
- safe enough to hand off to a nontechnical owner
- structured enough to review by mentors and sponsors
- open enough to fork for any chapter or community group
Contributions are welcome if they improve real-world usefulness for under-resourced organizations. The best issues include:
- a real user or chapter scenario,
- before/after evidence,
- privacy and accessibility considerations,
- a test or release-checklist update.
Read CONTRIBUTING.md, SECURITY.md, and CODE_OF_CONDUCT.md before opening a PR.
MIT License. Built by Volta for public benefit.
Designed in Jacksonville. Coded globally. Built for digital equity.