1.0.0 Roadmap

[benmerckx]

Missing features

• Self-hosting: instead of the modular approach we had I think we can go with a single well-tested setup where we require both a Github token (or Github deploy key) and some persistence (database or redis)
• Moving entries (Sort/move entries #13)

Confusing APIs: we have a final call to break these before we're tied to supporting them for the long term

• Re-think createCms vs createNextCms. Evaluate what we need to support other frameworks and see if we really need the distinction here. Once option is changing the import based on framework (from 'alinea/next', 'alinea/remix').
• Collection config style #373
• Boolean arguments are sometimes prefixed with is (Type: isHidden, isContainer) and sometimes without: (Field: hidden, readOnly)
• The query engine is quite complete in functionality but now it needs to become intuitive as well. I think only selecting from linked Entries is todo here.
• There's still potential for name-clashes in the List and Link field which will combine your fields and the internal things such as id, index and type. Can we restructure data to avoid this completely? (Validate naming #29)
• Clean up the exports from the alinea package. It would be nice to be able to import * as alinea from 'alinea' because it will help with tree shaking. I think we could still support the current default export as well.

Documentation

• Document usage in Next.js edge routes
• Examples/starters, featured on the website

Test scaling

• Are we ready for 10k, 100k entries?

External

• Seems Next.js is not bothered to support smaller packages for now, but one can hope: Add alinea to server-external-packages.json vercel/next.js#55006
• Making sure custom fields and views are excluded form website bundle requires: Unused client components are added to a client's bundle in app router. vercel/next.js#50285
• Previews are flaky in production: Enabling draft mode causes "Invariant: expected pageData to be a string, got undefined" vercel/next.js#61377

Nice-to-have

• (Next) merge backend and preview into a single handler
• Finish and document how to seed pages.
• Integrate images and columns deeply into the Rich text field. I think there's a great opportunity to make those "primitive" content blocks that can be rendered just as easily as the other content types (heading, paragraph, ...).
• Focus point selection for images.
• Adding extra fields to the MediaFile type.
• Design?
• Validate locales with Intl.Locale
• Translate the dashboard UI
• The Link vs entry, file, image, url field api is not super intuitive. It'd be nicer to wrap them so we can also target the configuration of each link picker much better:

alinea.link(  
  alinea.image('Pick an image'),  
  alinea.file('Or a file')  
)