Internal planning route

SeriousDesign Roadmap

One plain-text roadmap, one internal route. This page mirrors todo.md so progress stays easy to edit and easy to review.

Updated 2026-03-07
Sections 8
Action items 48
Ordered steps 13
01

Recently shipped

6 items
  • Multilingual routing and localized content foundation for the main public pages.
  • A cleaner language switcher and a stronger mobile layout for the homepage technology stack.
  • Homepage motion and reveal effects to make the landing experience feel more alive.
  • A redesigned tools page with curated visibility, better contrast, and Spanish cleanup.
  • An interactive `/project-request` flow with branching questions, estimator output, local draft recovery, and server-side draft storage.
  • A reusable Playwright click-through QA scaffold for public routes.
02

Now

4 items
  • Validate the new homepage services section against real content priorities and conversion goals.
  • Turn `/project-request` from draft capture into a real submission flow.
  • Externalize the remaining hard-coded public copy into editable locale content files.
  • Review metadata, canonical tags, and hreflang output across the localized routes.
03

Services intake follow-up

3 subsections

The homepage now exposes a wider service catalog. The next question is whether lead capture should branch by service or stay unified.

Shared-form path

  • Keep one primary intake flow for all services and prefill the selected service when the user enters from a service card.
  • Add a hidden `service_interest` field plus visible context in the summary and internal notifications.
  • Reuse the current `/project-request` structure for strategy, delivery, and software-heavy services where scoping matters.
  • Route lower-friction services such as SEO audits or maintenance to the contact form with a shorter service-aware variant.

Custom-form path

  • Create service-specific entry points only when the questions diverge enough to improve qualification quality.
  • Candidate services for custom forms: project management, AI agent implementation, web scraping/data extraction, and site auditing/SEO.
  • Keep the backend submission schema shared even if the front-end forms differ, so triage and storage stay consistent.
  • Avoid building ten separate forms unless routing data proves the generic flow is losing qualified leads.

Suggested improvements

  1. Add query-param or route-state support so each service card can open a form with service context already selected.
  2. Decide on a form matrix: `contact`, `project-request`, or `custom intake` for each service.
  3. Add service-specific CTA copy in the forms so the landing context is preserved after click-through.
  4. Store the originating service on every submission for reporting and later conversion analysis.
  5. Test whether shorter forms improve response rate for operational services like maintenance or SEO.
04

Project request roadmap

2 subsections

Done

  • Four-step interactive brief flow.
  • Conditional questions based on project type.
  • Estimator summary for project size, urgency, recommended stack, and engagement shape.
  • Local draft persistence with resume or start-fresh recovery.
  • Explicit save action that writes a readable draft file on the server.

Next

  1. Add a final submit endpoint separate from draft save.
  2. Store submissions in a structured format for later review.
  3. Send internal notifications after successful submission.
  4. Add inline validation and clearer per-step error handling.
  5. Improve the mobile summary experience.
05

Multilingual cleanup

4 items
  • Move the remaining active Twig copy into locale JSON files.
  • Review secondary pages for English leakage on `/es/*` routes.
  • Decide whether `/todo` stays internal English-only or gets localized wrapper copy.
  • Add more locale-specific QA coverage for shared UI states.
06

QA and release

4 items
  • Reuse the Playwright foundation on Drupal projects with role-based workflows.
  • Add authenticated fixtures for institution manager, institution approver, and blog creator flows.
  • Run smoke coverage for home, tools, contact, and project request before releases.
  • Add reduced-motion and mobile viewport checks to the default QA pass.
07

Backlog

4 items
  • Replace the placeholder blog with a real content pipeline.
  • Add portfolio or case-study pages.
  • Decide the future scope of `/boards` and whether it stays public.
  • Review typography and spacing consistency after the recent feature work.
08

Guardrails

3 items
  1. Keep roadmap content easy to edit in plain text first.
  2. Avoid duplicating planning copy inside Twig when the markdown file can stay the source of truth.
  3. Keep internal routes like `/todo` informative but not indexed.