Since the release of 0.1.0-beta.8 on 2/28/2025, StudioCMS has undergone significant improvements across performance, security, content management, and developer experience. Let’s dive into the most important updates from versions 0.1.0-beta.9 through 0.1.0-beta.15.
Performance Enhancements
'Read the “', Performance Enhancements, '” section'- Concurrent Data Processing: Optimized data processing with concurrent operations for faster content rendering and improved responsiveness (#544)
- Route Optimizations: Variables called on multiple pages/endpoints were moved to middleware for better performance (#545)
- SDK Pagination: Added pagination support to improve performance when fetching large sets of pages (#539)
Content Management Improvements
'Read the “', Content Management Improvements, '” section'- HTML Page Type: Added a new HTML pageType with SunEditor HTML builder for creating HTML pages (#480)
- Improved Page Management: Refactored createPage logic to better handle draft and published pages (#538)
- Enhanced Diff Page: Updated the diff page with better display of metadata and interactive buttons for reverting changes (#485)
- Component Names: Components in componentRegistry can now have names with hyphens (e.g.,
test-comp) (#537)
Security & Authentication
'Read the “', Security & Authentication, '” section'- Improved JWT System: Introduced a new JWT Token system that reduces dependencies (#504, #522)
- User Permission Verification: Enhanced security by verifying user permissions before allowing modifications (#536)
- Password Recovery: Implemented forgot password functionality when the mailer is enabled (#461)
- Email Verification: Extended mailer functionality for optional email verification (#459)
User Management
'Read the “', User Management, '” section'- Avatar Improvements: Added ability to update Avatar URL and sync with Libravatar Avatar service (#529)
- CLI User Management: Implemented CLI utilities for user management (#517)
- User Notifications: Implemented basic email notification system for users and administrators (#460)
Developer Experience
'Read the “', Developer Experience, '” section'- New Rendering System: Refactored the rendering system to rely on plugin PageTypes instead of the built-in system, enabling easier integration of new page types (#478)
- SDK Enhancements:
- Buildkit Integration: Updated to utilize new
@withstudiocms/buildkitfor build and development (#512) - Runtime Functions: Exported runtime functions in package.json for plugins to use (#506)
Email Integration
'Read the “', Email Integration, '” section'- SMTP Configuration: Implemented new SMTP
nodemailerconfiguration for sending emails (#457) - Email Templates: Updated email templates and improved handling of email sending errors (#462)
Internationalization
'Read the “', Internationalization, '” section'- Localization Updates: Multiple translation updates across versions (#510, #528, #543)
- Default Language Update: Changed default
en-uslanguage code toen(#511) - Client-side i18n: Implemented nanostore i18n client-side system (though currently only the base locale “en-us” is available) (#446)
Caching Improvements
'Read the “', Caching Improvements, '” section'- Version Cache: Fixed version cache generation (#524)
- Page Creation Cache: Fixed bug with page creation and cache (#531)
- SDK Cache: Improved cache busting to ensure freshness of data (#507)
Bug Fixes
'Read the “', Bug Fixes, '” section'- UI Enhancements: Fixed CSS for dashboard grid components that showed incorrect colors in some browsers (#527)
- Username/Password Validation: Re-enabled verification for usernames and passwords to ensure data safety (#476)
- WebVitals Plugin: Fixed translations for the dashboard page (#514)
Breaking Changes
'Read the “', Breaking Changes, '” section'- Rendering System: The new rendering system requires passing the entire PageData object instead of just the content (#478)
- Built-in Renderers: Removed MDX and MarkDoc from built-in renderer (these will be replaced by plugins) (#478)
- Schema Updates: Some non-breaking schema updates require running
astro db push --remote(#507)
Infrastructure Changes
'Read the “', Infrastructure Changes, '” section'- Asset Relocation: Static assets were moved to a CDN R2 bucket, meaning users can delete the
studiocms-resources/folder from their project’spublic/folder (#432) - Dependency Cleanup: Removed unnecessary dependencies like
package-jsonin favor of simpler interfaces (#505)
What’s Next?
'Read the “', What’s Next?, '” section'With these updates, StudioCMS continues to evolve into a more robust, performant, and developer-friendly content management system. The focus on plugin-based architecture, improved rendering, and enhanced security features demonstrates the team’s commitment to building a flexible and powerful CMS for the modern web.
As we get closer to being able to drop the -beta.x versioning, our goals are aimed completely towards knocking out any bugs we come across, as well as completing all the in-progress functionality and features we are working on, including translations for the dashboard allowing even more global reach for our users.
We also have various Experimental plugins that are already making StudioCMS even more useful, including a WYSIWYG Page Builder, and Social media cross-poster, which is useful for when you publish a new post, and want to be able to easily let various different platforms know without loggin into each one. With even more planned in the near future!
Stay tuned for updates on our GitHub There is also our Discord Server for more regular updates, chat and support.
Remember to run astro db push --remote after updating to ensure your database schema always stays in sync.
Adam Matthiesen
Published 4/9/2025Back to Blog