Skip to main content

Limits and roadmap

Stated plainly, because finding these out mid-project is worse than reading them now.

Limits, honestly​

Deploy latency is the real UX risk. Publishing feels broken without the "live in about two minutes" messaging. Do not remove it.

"No admin pages" has exceptions — /admin, the floating toolbar, collection management. The line is: the client edits on the real page, and never creates pages.

Clients cannot create pages. Collection items only; pages are dev-authored. A client who needs to add pages needs a different CMS.

next.config needs a dev-server restart when allowedHosts changes, because Next reads it once at process start.

Repo growth from images. Every upload is a permanent blob in git history. Point heavy users at remote URLs.

No merging. Concurrent edits are rejected, not reconciled. For a single-client site this effectively never fires; for a site with several simultaneous editors it will.

Sessions need a secret in production. Set COPY_INK_SESSION_SECRET and sign-in is a signed cookie that any instance can verify. Leave it unset and sessions live in one process's memory, so serverless or multi-instance hosting signs a client out mid-edit. See Sessions.

Editing is a popover, not in-place. contenteditable fights paste-with-styles, IME input, mobile keyboards and React's controlled inputs. The popover gives most of the perceived magic for a fraction of the bugs.

Not in v1​

  • Branch and PR publishing
  • Preview deployments per changeset
  • contenteditable in-place editing
  • GitLab, Gitea and Forgejo adapters
  • Video and file uploads
  • Client-created pages
  • Scheduled publishing
  • Field-level history from git log

Nothing on that list is blocked by the architecture. ContentBackend and AuthProvider are the two extension points, and both are small.

What will not change​

  • <Copy> stays plain-text-only. Markdown belongs to <Copy.Rich>.
  • Production output stays free of editor markup.
  • scope stays absolute. One rule, no exceptions.
  • Pages Router stays unsupported.
  • Image hosts stay opt-in — auto-appending a host would turn the Next image optimizer into an open proxy.