Back to selected work

Existing demo · expansion planned

Template Studio

Source updated

A document workspace with rich-text editing, template variables, desktop/mobile previews, browser-local drafts, and sanitized HTML export. System, light/dark themes, and increased contrast.

Template Studio — local development version
Local development version, 14 October 2026. The deployed demo may differ.

Project context

A browser-local document workspace with a self-hosted HugeRTE editor, template variables, preview modes, and HTML export. Drafts stay in the current browser; export is needed to keep a copy elsewhere.

Existing implementation

A document workspace with rich-text editing, template variables, desktop/mobile previews, browser-local drafts, and sanitized HTML export. System, light/dark themes, and increased contrast.

  • React
  • TypeScript
  • Vite
  • HugeRTE

Planned improvements

Document editing and preview behavior, then improve validation, keyboard access, and recovery from errors. Add AI-assisted drafts only after the baseline is tested.

Decisions to document

State ownership, the template schema, preview updates, validation feedback, and the boundary between generated drafts and user-approved changes.

Accessibility testing

Status: not yet audited for this case study. The next report will record date, browser, assistive technology, tasks, findings, fixes, and remaining limitations.

AI-assisted drafting · planned

Describe a template, receive a validated draft, review the proposed changes, and choose whether to apply them. Invalid output, cancellation, provider failure, and keyboard/screen reader feedback are part of the acceptance criteria.

  1. Document the baseline. Explain the editor’s user task, architecture, ownership, and limitations.
  2. Test and improve accessibility. Test complete keyboard and screen reader tasks; fix and retest findings.
  3. Build reviewable AI drafts. Validate structured output, show a draft preview, and require explicit application.
  4. Evaluate and publish. Publish quality, latency, cost, failures, and a dated maintenance note.

Evidence and limitations

The project links and original technology descriptions are available at the top of this page. No production outcomes, performance improvements, or completed accessibility audit are claimed on this page.