J json-to-dom
Roadmap & guardrails

Tasks & scope.

json-to-dom is intentionally narrow, fast, and zero-dependency. Priorities, follow-ups, and guardrails guide its evolution.

Current priorities

  • Keep the core compiler zero-dependency and ultra-fast.
  • Keep documentation and live samples synchronized with the active v11 engine.
  • Maintain strict KeshavSoft { in... } / local... parameter standards.
  • Ensure transparent runtime event inspection (getHookedEvents, __ksEvents).

Useful follow-ups

  • Expand tag definitions in tags.json for modern semantic elements (dialog, details).
  • Benchmark performance against raw imperative DOM construction.
  • Provide additional live gallery templates for nested cards and data grids.
  • Enhance CLI copy feedback and scaffolding presets.

Scope guardrails

  • Do not add external npm runtime dependencies.
  • Do not introduce a heavy Virtual DOM reconciliation engine.
  • Do not turn the repo into an all-in-one application or routing platform.
  • Preserve the strict serializable boundary: JSON in, DOM out.

Project intent: json-to-dom remains a pure, reliable, zero-dependency compiler for declarative DOM generation.