Milestones
List view
A framework-agnostic core, with React and Next.js support. Extract the client, router and schema into @druxt/core so renderers are peers. GraphQL gets its decision here. Scoping starts after 2.0.0 is stable.
No due date•0/2 issues closedWebform and Page Manager support, the two features agencies ask for most. Both are contrib modules built on the 2.x stack. Sequenced last so the new architecture is proven first.
No due date•0/2 issues closedContent editor experience. Decoupled preview, Layout Builder and Decoupled Menus. Preview is a core offering, off by default. Layout Builder graduates from an example to a contrib module.
No due date•0/3 issues closedAccessibility and content modelling. Aria and visually hidden field labels, metatags, path alias and redirect support, field groups in the schema, standard Views pagination, and a DruxtSite scaffolding CLI.
No due date•0/7 issues closedStore and client hardening after the 2.0.0 rewrite. Work that depends on the new store model or is cheapest right after it lands: cache invalidation, CRUD client methods, store flush on logout, front page route override, v-model support, schema regeneration and schemas in code.
No due date•0/11 issues closedFuture features and improvements to Druxt core modules. E.g., Load More style Views, decoupled entity fields, etc.
No due dateNuxt 3/4, Vue 3 and TypeScript rewrite. Packages move to the @druxt/* namespace. The main focus once 1.0.0 ships. Feature requests get a ship or defer decision when this milestone is scoped, not before. Codename: Beguiling Belatrix
No due date•0/9 issues closedIterative improvements to be added after the first official release.
No due dateThe first stable release of DruxtJS. Scope is frozen: bug fixes, documentation and release tooling only. New features land in 2.x. Point releases (0.x) along the way are fine. Codename: Avenging Albus
No due date•22/37 issues closed