Roadmap

The roadmap is a fit check, not a promise sheet.

QuillDock uses this page to show the current launch boundary, the deferred capabilities under evaluation, and the feedback path for workflows that are still out of scope.

What is supported now

  • Google Sheets and Airtable
  • One active source entity to one active target collection
  • Existing target selection and real collection bootstrap
  • Trusted preflight, manual publish, automatic backups, and restore-aware recovery
  • Scheduling after one successful manual publish on the current configuration
  • Single image, single file, and bounded single reference support

What we are evaluating next

  • Multi-reference support where the resolution model stays bounded and supportable
  • Richer content shapes that do not turn QuillDock into a generic object-sync platform
  • Workflow refinements that reduce review time without weakening the trust posture

This page is a demand-shaping surface, not a promise sheet. QuillDock does not attach dates or guarantees to deferred capabilities here.

Tell us what would unblock you

If a deferred field type or workflow is the only thing stopping your launch, start with the support docs and tell us what collection shape, field type, and outcome you need. That keeps roadmap requests grounded in real publish work instead of abstract wish lists.

Keep the signal concrete

The most useful roadmap request is the one tied to a real publish flow.

If you need more than the current launch surface, tell QuillDock what source shape, target collection, and blocked outcome are involved. That helps separate real demand from vague scope creep.

The fastest next step is usually one of these: