Your Ideas Shape 
Classic Monks

It would be great if there was an option to ensure that the preloader plays only once per session. Currently, it plays every time someone clicks on the “Home” button, even though I’ve set it to display only on the homepage. This is excessive for users who are already on the website, and it’s not a pleasant experience for the website to load every time.

Whenever an image is added to a post, WordPress automatically saves it in a medium size. It would be beneficial if the image could always be uploaded in full size, ensuring that the image remains sharp and clear.

It would be incredible to have a built-in Structure Audit overlay tool directly in Classic Monks. As a developer, I constantly need to audit HTML5 landmarks, heading hierarchy, accessibility compliance, and content structure, but currently I have to rely on browser extensions or external tools that don’t integrate well with my workflow.

1. We’re excited to share that we’re actively developing Quick Monks Command – an intelligent command palette system that’s going to transform how developers and power users navigate WordPress. Think of it as Alfred meets WordPress admin, built specifically for our WordPress and Classic Monks ecosystem.

Enable seamless integration to automatically offload WordPress media uploads to external cloud storage providers such as Amazon S3, DigitalOcean Spaces, or Google Cloud Storage. This feature would allow users to save local server space, scale storage cost-effectively, and improve media delivery performance. Users could choose their preferred cloud provider, set bucket/folder paths, and configure access permissions right from the Classic Monks interface.

It would be fantastic to have an easy, lightweight Custom Fields feature built right into Classic Monks, similar to how ACF works. This would let users quickly create and manage custom fields like text, image, select, etc. for posts, pages, or custom post types without needing bulky plugins. A simple UI for field creation, flexible placement options, and some basic conditional logic would really help developers and content creators build custom layouts and dynamic websites much faster. A native version focused on performance and simplicity would save a lot of time and keep Classic Monks sites bloat free!

It would be a game changer to have a feedback tool right on the site, similar to Figma comments, where clients and team members can leave feedback directly on live designs. This would allow users to click on any part of a page, drop comments, ask questions, or suggest changes in context making the review process smoother. Threaded replies, tagging, and real-time notifications would make it easy for teams to discuss design tweaks, and clients could point out exactly what they want changed without endless email threads. This feature would seriously improve collaboration and help deliver exactly what clients want, faster and with less back and forth!

Create a simple and, native subscription system inside Classic Monks, no third-party plugins needed. Let users easily set up and manage recurring payments and memberships with a easy to use, performance friendly solution.

Add stylish, ready made layouts for WooCommerce subscriptions, clean pricing tables, modern membership options, and quick style presets. Make it easy to create beautiful, branded subscription pages without any custom CSS.

Add an option to enable excerpts for pages and show an excerpt column in admin lists and quick edit.

Provide an option to disable attachment pages and redirect to parent post or media file.

Disable or hide publicly accessible author archive pages to improve privacy and reduce information disclosure.

Add a modern responsive gallery layout optimized for listing images with full-screen viewing.

Add tools to delete single or multiple post revisions to reduce database size.

Add a built-in dark mode for the WordPress admin interface to reduce eye strain.

Provide a customizable coming-soon/maintenance page that can be enabled without extra plugins.

Generate secure temporary login links with expiration for support or short-term access.

Add guided tours or next-step highlights to onboard users and explain features inside the admin.

Allow displaying product variation options (like size/color) directly on archive/shop listing pages.

Detect broken links inside Bricks content stored in post metadata and provide tools to fix them.

Allow selecting and assigning multiple user roles during account creation or editing.

Set custom post-login or post-logout redirect URLs based on user roles.

Display all generated image sizes and their dimensions when editing media to simplify optimization decisions.

Allow configuring heartbeat frequency per area (editor, front-end, etc.) or by site location.

Allow configuring revision settings per post type or globally, including limits or disabling.

Scans the site for potential security vulnerabilities and provides clear remediation steps.

A lightweight form builder to quickly create contact, feedback, and simple data collection forms without extra plugins.

Disable or hide publicly accessible author archive pages to improve privacy and reduce information disclosure.

Allow user switching only between specific allowed roles or accounts.

Detect scheduled posts that failed to publish and automatically attempt to re-publish them.

Expand and improve translation files to support additional languages and locales.

Provide more options to customize the admin footer text, links, and layout for branding.

Automated Database Cleanup: Ability to remove unnecessary data such as post revisions, trashed items, spam comments, expired transients, and orphaned metadata.
Table Optimization: Optimize database tables regularly to improve efficiency and reduce overhead, especially for MyISAM tables (noting that InnoDB handles some optimization automatically).
Scheduling Options: Provide flexible scheduling (daily, weekly, monthly) for automatic database maintenance tasks.
User Notifications: Optional email or dashboard notifications upon completion or failure of optimization tasks.
Compatibility: Ensure compatibility with popular storage engines (InnoDB, MyISAM) and WordPress multisite installations.
Safety Measures: Include safeguards such as backup reminders or integration with backup plugins before optimization runs. This feature would help users maintain a clean and efficient database, improving website speed and stability without requiring manual intervention.

Make upload filenames lower ( add_filter( ‘sanitize_file_name’, ‘mb_strtolower’ ); )

Disable admin top bar for user roles

Remove “WordPress” from admin titles

Add the Page Slug to Body Class

Enable pages, posts and/or custom post types to have permalinks that point to external URLs. The rel=”noopener noreferrer nofollow” attribute will also be added for enhanced security and SEO benefits. Compatible with links added using Page Links To.

Show quick summary of the system the site is running on to admins, in the “At a Glance” dashboard widget. This includes the web server software, the PHP version, the database software and server IP address. It will also show the size of the site, database, root, wp-content, plugins, themes and upload folders.

Display a panel showing and linking to all available sizes when viewing an image in the media library. Especially useful to quickly get the URL of a particular image size.

Return 404 (Not Found) error when trying to load author archives. Remove or disable links to author archives. Remove authors archives from the sitemap.

Option to redirect user after logout to custom URL.

Option to redirect user after login to custom URL.

Option to open all external links in new tab.

Frontend logo in the top bar to redirect to the wp-admin (link back to the dashboard when it is shown on the frontend).

Switch to user (customer) from the order edit.

I would like to suggest adding a login redirect feature to the Classic Monks plugin. The idea would be to allow administrators to define a custom admin page or panel that users are redirected to immediately after logging in, instead of always being sent to the default WordPress Dashboard.

In my case, I use LatePoint as a booking plugin, and I would like agents to be redirected directly to the agenda page of the plugin when they log in. Currently, they are first sent to the WordPress Dashboard, which adds an unnecessary extra step and can be confusing for users who never need to access the dashboard itself.

Having a simple option to set a custom post-login destination—either globally, per user role, or per account—would greatly improve the user experience. This would be especially useful for sites that rely heavily on specific plugins or custom panels and want to streamline workflows for staff or clients.

Even a basic implementation, such as selecting a target admin URL for certain roles, would add significant value while keeping the feature lightweight and easy to configure.

I would like to suggest adding a simple option to manage the Open Graph image and meta description directly within the Classic Monks plugin. Currently, changing these requires installing a full SEO plugin, which feels unnecessary for users who only need control over these two elements.

A lightweight setting that allows users to define the Open Graph picture and meta description would be sufficient for many use cases, especially for smaller websites or users who prefer to avoid plugin overload. This would make it easier to control how pages appear when shared on social media or displayed in search results without the added complexity of a complete SEO solution.

Implementing these basic options would provide practical value while keeping the plugin minimal and focused.

It would be great if the Classic Monks Image Conversion feature could support generating multiple image formats with configurable fallbacks, instead of forcing a single output format.

Proposed behavior:

• Generate AVIF
• Generate WebP
• Keep the original JPG / PNG
• Optionally keep other formats (GIF, BMP, etc.)

Images would then be served in priority order based on browser support:

• AVIF → WebP → JPG/PNG
  or
• AVIF → JPG/PNG (simpler fallback)

This would allow site owners to start with multiple formats, monitor real-world browser support via analytics, and then make informed decisions later. For example, once AVIF support reaches ~90% of visitors, WebP versions could be safely removed, leaving just a single fallback.

Why this matters:

• Better performance without locking users into a single format
• Safer rollouts for AVIF adoption
• Full control over storage vs. compatibility trade-offs
• Cleaner long-term media management based on actual data

Ideally, this would be configurable per site (or globally), with simple toggles for which formats to generate, which to serve first, and whether older formats can be automatically cleaned up later.

It would be fantastic to see a customizable Right Elements Shortcuts panel added to Classic Monks for Bricks Builder. Allowing users to pin their most frequently used elements for one-click access would greatly improve workflow efficiency, reduce repetitive searching, and speed up page building.

It would be great if Classic Monks introduced a built-in version history system similar to Git. The ability to create named snapshots, compare changes, restore previous versions, and work with Development and Production versions would make Bricks workflows much safer and more efficient. This would be especially valuable for freelancers and agencies working on complex client projects.

Add support for Etch (https://etchwp.com/) with similar enhancements like you have for Bricks.