Requests

Add first-class support for PostgreSQL and SQLite alongside MongoDB, so developers can choose the database that fits their infrastructure without losing any core CMS functionality.

Modernize the ApostropheCMS CLI and instrument it with privacy-first telemetry so we can measure and improve the developer onboarding experience.

Unified AI adapter pattern giving developers a single, provider-agnostic API for all AI features, with configurable effort levels and multi-provider support.

In Apostrophe 2, we supported drafts in Document Versions but many found it too cumbersome. Still, to support common editorial workflows, it would be useful to support drafts in some way.

Improve document version history to give editors greater visibility and confidence in tracking and managing content changes.

Our localization and AI-powered translation flow needs to be improved to support the refinement of content across locales. Related: More granular changes tracked in document versions.

A feature that accelerates content creation by bringing AI magic to page, piece, layout and content creation while respecting projects' custom widgets, templates, and configurations.

This feature would make it easy to create Alt Text on new images, and review the site for images with missing alternative text and generate image descriptions in a click or two.

Swatches are currently only named as their HEX codes, but brand teams usually have names for these colors and specific context for them to be used. This enhancement would improve the color picker feature used in rich text and Palette to allow naming.

As a user, working on a draft document perhaps over days or weeks, I should be able to see which fields have changed relative to the published version of the document. In addition I should be able to "drill down" and see this at nested levels. For instance, if I see that an area has changed, I should be able to open the widget editor for an individual widget and see which fields of that particular widget have changed. The same applies to nested objects and arrays.

ApostropheCMS allows the archiving of images, but hard deletion from the database is not yet supported. We're considering whether being able to view all linked documents before deletion is critical or could be phased in.

Make image optimization easy, eliminating manual conversion workflows and delivering performance improvements by converting media to webp.

Currently under review

Support for MCP, an open standard for connecting AI models to dev tools and data sources, would allow AI systems to safely understand and interact with ApostropheCMS — unlocking schema-aware content generation, automated optimization, and more.

Though we have Advanced Permissions and paths for manually creating a "super admin" role for Assembly customers, this could be made much simpler. The goal is to easily give access to users and/or groups full access to all Assembly sites.

Currently under review

Currently under review

The ability to set some parameters around document versions would help keep the number of saved versions under control. Examples include setting a max threshold and removing the oldest version when a new one is saved.

Currently under review

Currently under review

Designers working for organizations that frequently extend and customize ApostropheCMS features and front end would love access to an Apostrophe UI kit to jumpstart ideation and prototyping.

Right now, you can restrict access to any page or piece by setting "Visibility" to "Login Required," but it should be possible to grant permission to individuals and groups, just like you can grant "edit" permissions to individuals and groups.

ApostropheCMS supports archiving (or soft deletion) rather than hard delete as the primary UI for deletion. For content that is localized and not autopublished You can then "delete draft" from the archive fiew.

There are times when editors need to modify the AI-generated content more than just formality of tone. Deepl's Glossary feature provides more control over tone and conventions, and support would be a nice default feature for Automatic Translations.

This would add a new "Custom" option to the dropdown of available aspect ratios, and when selected, additional fields for width/height appear so the editor can input their custom aspect ratio. The crop box would adjust accordingly.

Currently under review

Slug is an important piece of information when working across locales, and should be shown within the page manager view.

The most narrow widget editor modal width is too narrow, and editors cannot change this themselves. It would be better to be able to have some control in the case where a widget is complex (big) or the modal is in the way.

Currently under review

Currently under review

In Apostrophe 2, we had an SEO scanner that hasn't yet been ported to the modern version of Apostrophe. This could be an integration instead.

Currently under review

ApostropheCMS's video widget supports YouTube and Vimeo, but there are times when an uploaded video is necessary. Background videos are a good example.

In Apostrophe 2 you could bulk upload files, which is something not supported yet in the modern version of Apostrophe.

Currently under review

This is about offering clearer documentation around commands for our Automated Tests extension.

Making a "clear formatting" option default in the rich text toolbar could help reduce confusion for editors.

When deleting a document (article, page, image) it would be nice to see all of the locations that would be impacted on the site.

Currently under review

Currently under review

For projects with hundreds of pages, or even just dozens, it would be helpful to be able to search pages just like you can pieces.

Currently under review

Blogs are already supported, but we want to make it faster to spin one up. This work is focused on ensuring developers don't have to do a lot of work to get standard blog features working.

Currently under review

The majority of the current documentation is for developers. While each site is going to have unique features, a set of documentation featuring common Apostrophe tasks would help onboard editors more quickly.

A visual schema editor for developers essentially serves as an accelerator for editing the project code, therefore it doesn’t change workflows or require Apostrophe’s internal startup procedure to be overhauled.

Adds new tools for organizing and browsing media in the Media Library, such as folders and/or improvements to the way Image Tags work.

We already have a fully featured REST API that supports headless and decoupled applications, but are interested in adding GraphQL support as well.

Currently under review

Currently under review

Useful activity monitor for batch and long running operations

Currently under review

Currently under review

Currently under review

Currently under review

Currently under review

This is about more clearly showing the relationships so that when a piece is edited, deleted, etc. editors know every part of the website that will be impacted.

Rather than prevent someone from uploading an image that's too small, or hiding it in the Media Library, scale it up automatically and allow them to move forward.

Automatically translating content importing into multiple locales is already supported, but does require separate imports for separate languages. This flow could be updated to be even faster.

In Apostrophe 2 we allowed users to filter media by orientation type so that they could find the right photo for their page. Adding this and a filter by multiple tags feature would improve media filtering in ApostropheCMS 4.x.

Adds new defaults to ApostropheCMS's rich text toolbar, including emojis, highlight color, code syntax.

Currently under review

Content leaders need the ability to edit prompts per locale so that more than just language is factored into AI-powered translations: tone, formality, and more are critical to getting first drafts with AI right.

Make simple modifications to images using AI, such as removing backgrounds.

This would allow editors to select multiple pieces or pages, and schedule them all to go live at the same time.

Default structured data fields and simple customization techniques to add industry-specific data will empower teams to follow structured data best practices faster and easier.

Give content managers more control over presentation attributes such as colors, borders, and padding. Widget Styles will introduce default options to our core widgets and make it fast and easy for developers to add style fields to their custom widgets.

Support for rendering RTL content on the public-facing page, and managing RTL content within an LTR admin UI.

Static builds will allow customers to pre-render static sites in the traditional Astro way, as opposed to running Astro with its Node adapter and a live ApostropheCMS server.

Currently under consideration.

Tables are a common element of websites, and we want to make it easier to do more basic table structuring on the page after inserting it. This would add common tools like cell merging, add columns, resize columns, etc.

A series of mini tutorials aimed at helping new ApostropheCMS developers take shortcuts and understand best practices for delivering a great editor experience.

Add a shortcut to access editing controls for any custom widget to the context menu. This is the first step in our Sections feature, but the feature supports all widgets.

ApostropheCMS's rich text toolbar is customizable, and while our approach has been to keep it minimal and let product teams decide, we've learned that offering more options with no configuration needed could make life easier for product teams.

Bumping the visibility of image controls and making more common features turned on by default is the goal of this set of work.

This would add links to the default image schema by default, so that editors can add links to images without any extra configuration from a developer.

Adding intuitive keyboard shortcuts to the in-context editing experience will help speed editing workflows. Editors will be able to Copy widget (⌘+ C or ⊞ + C), Cut widget (⌘+ X or ⊞ + X), Paste (meta+v), Duplicate (meta+shift+d), Remove (backspace)

To improve media organization in ApostropheCMS, we're adding batch tagging so that an editor can select multiple images to be sorted under the tag(s) of their choice.

What we typically call "Layout widgets" allow you to add columns in different configurations and place widgets inside are common in ApostropheCMS. Layout, a new core widget, allows you to create, resize, move and remove columns with ease.

Sometimes it's necessary to have a nicer, customizable URL for file sharing.

Currently under consideration.

Apostrophe Pieces currently support batch editing, along with a pattern to add your own batch operations to the CMS, but this doesn't currently extend to the Media Library.

Currently under consideration.

Drag an image from your computer onto an image widget to add that image.

Currently under consideration.

This request came from Go7 as an alternative to automatic translations, because their clients prefer to work with human translators.

Similar to the Document Template Library, this feature would give admins the ability to save a group of widgets from the editable area of page to a content library. This would enable re-use of widgets or nested widgets as "elements."

See changes on the page as they are being made in the Widget Editor. This is intended to improve the experience of working with content for editors.

Adding the ability to translate imported documents with AI.

Empower global content teams to efficiently track, access, and manage recently localized and edited content, reducing the time to find and act on documents from hours to seconds.