NextPress Development Roadmap

NextPress is an open-source, self-hostable content management system that brings the flexibility and familiarity of WordPress to the modern JavaScript ecosystem.

Our goal is to build a powerful, extensible CMS that is easy to use, customize, and develop for, while embracing modern web technologies.

This roadmap outlines our current development priorities and longer-term direction.

Note: This is a living roadmap, not a fixed release schedule. Priorities may evolve based on technical challenges, community feedback, and contributions.

🔨 Now — Stabilizing the Foundation

1. Page Editor Stability

Goal: Deliver a reliable, intuitive, and production-ready visual editing experience.

The page editor is at the heart of NextPress. Our immediate priority is improving its stability, consistency, and usability.

Planned improvements:

  • Fix known bugs and inconsistencies in the visual editor.
  • Improve drag-and-drop behavior and block positioning.
  • Ensure consistent rendering between the editor, preview, and published pages.
  • Improve undo/redo and autosave reliability.
  • Refine responsive editing across desktop, tablet, and mobile.
  • Improve performance when editing complex pages.
  • Expand automated testing and regression coverage.

Success criteria: Users can confidently create, edit, preview, and publish pages without losing content or encountering unexpected layout changes.

🚀 Next — Expanding Core Capabilities

2. Improved Multisite Support

Goal: Make it easy to manage multiple independent websites from a single NextPress installation.

NextPress already includes foundational multisite functionality. We plan to expand this into a more complete management experience.

Planned improvements:

  • Improve site creation, configuration, and management.
  • Strengthen separation of content, settings, and media between sites.
  • Improve custom domain configuration and routing.
  • Refine site-specific user roles and permissions.
  • Simplify switching between sites in the administration interface.
  • Improve API consistency across multisite environments.
  • Expand multisite testing and documentation.

Success criteria: Administrators can confidently operate multiple websites through one installation while maintaining clear separation between sites.

3. Templates

Goal: Enable reusable page layouts and dynamic content rendering.

NextPress includes an experimental template system. Our focus is to make templates more powerful, consistent, and accessible.

Planned improvements:

  • Stabilize the existing template system.
  • Improve template creation and editing through the visual editor.
  • Expand support for dynamic content and template variables.
  • Improve conditional template rendering.
  • Support reusable layouts across multiple pages and posts.
  • Provide starter templates for common website structures.
  • Improve template documentation and developer tooling.

Success criteria: Users can create reusable layouts and apply them consistently without rebuilding pages from scratch.

🌱 Later — Building the Ecosystem

4. Themes

Goal: Provide a flexible and developer-friendly system for creating, customizing, and sharing website designs.

Themes will allow developers and designers to customize the appearance of NextPress websites without modifying the CMS core.

Planned improvements:

  • Expand the existing theme system and template overrides.
  • Define a documented and stable theme structure.
  • Improve theme activation and management.
  • Support configurable theme styles and design settings.
  • Enable reusable theme components and layouts.
  • Introduce starter themes and developer examples.
  • Explore easier theme packaging, distribution, and installation.

Success criteria: Developers can build and distribute themes independently of NextPress core, and users can switch themes without losing their content.

5. Plugins

Goal: Establish an extensible plugin ecosystem that allows developers to add functionality to NextPress.

NextPress already provides foundational hooks and plugin management capabilities. Our long-term objective is to turn these foundations into a complete extension platform.

Planned improvements:

  • Formalize and document the plugin API.
  • Expand the action and filter hook system.
  • Support installing and loading external plugins.
  • Implement reliable plugin activation, deactivation, and removal.
  • Define secure and predictable plugin execution boundaries.
  • Allow plugins to extend the administration interface.
  • Provide plugin development tools, examples, and documentation.
  • Explore compatibility and migration paths for existing WordPress plugins where technically feasible.

Success criteria: Third-party developers can create, install, and maintain plugins without modifying NextPress core.

🔭 Ongoing Priorities

Alongside these milestones, we will continue investing in:

  • WordPress compatibility: Improving REST API compatibility and migration tooling.
  • Developer experience: Expanding the SDK, MCP integration, and developer documentation.
  • Performance: Improving rendering speed, efficiency, and scalability.
  • Security: Strengthening authentication, authorization, and extension safety.
  • Quality: Expanding automated tests, CI checks, and release validation.
  • Community: Making it easier to contribute, report issues, and propose improvements.

🤝 Get Involved

NextPress is an open-source project, and community contributions are welcome.

You can help by:

  • Reporting bugs and suggesting improvements.
  • Contributing code, tests, or documentation.
  • Testing experimental functionality.
  • Participating in technical discussions.
  • Building themes, templates, and plugins as the ecosystem evolves.

GitHub: https://github.com/nextpress-ai/nextpress

Website: https://nextpress.ai

Community: WhatsApp

Last updated: November 2026.