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.

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.

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.

We've offered hosting for a long time, but are excited to make the experience much more self-serve for our customers. Agency partners will beta test this feature before we release it to the public. Beta

Adding the ability to translate imported documents with AI.

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.

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.

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."

Gives developers the ability to add custom editing interfaces to a widget's in-context editing interface.

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.

This feature makes it possible to pre-save sections (blocks of widgets) so that editors can re-use layouts they like instead of building from scratch every time.

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

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

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.

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

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.

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.

Most of our customers want a blog, and we could do more to make it faster to spin one up.

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

The ability to drag/drop widgets to rapidly create layouts in context is something many CMSs offer now. There are risks that come with this approach - to performance, SEO, and more, but the ease of dragging is undeniable.

Advanced Permissions covers many different roles and Share Drafts allows for drafts of content to be shared with non-users, but we do not yet have a simple "view" role baked in Advanced Permissions.

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

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

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

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

ApostropheCMS already supports flexible and extensible integrations with third-party analytics platforms, allowing teams to track key metrics in their projects. We’re exploring a built-in analytics solution, particularly valuable for multisite deployment

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

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.

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.

This is about adding support for Bitbucket, so that you can connect projects to either Github or Bitbucket.

Useful activity monitor for batch and long running operations

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.