Hey Weavers,
We’re back with a new beta of RapidWeaver Elements 3. This is the fifth beta and fixes a few more new and long-standing issues.
As the beta has been well received and we’ve ironed out most of the newly reported issues, we think Elements 3 is now ready for prime time. In the coming weeks we’ll ship a new build that will be the first official non-beta release of Elements 3. Stay tuned!
What’s new in 3.0.5?
- Fixed alt text handling for custom and CMS image types
- CMS: Output now degrades gracefully when front matter is broken instead of failing
- Added hover-prefixed variants and mirrored scale options for properties
- Fixed the small border radius token incorrectly duplicating the Default value
- Ensured theme and design system values are consistently available to components
What’s New in Elements 3.0 so far:
- Upgraded to Tailwind 4.3.2
- Faster Preview and Export
- The Editor now preserves alpha transparency for WebP and AVIF images!
- Updated all themes to use Tailwind 4
- Updated border Radius and Shadow tokens to match Tailwind 4
- Update opacity utilities to use Tailwind 4 opacity modifiers
- Added Mauve, Olive, Mist, and Taupe colours from Tailwind 4 to all themes
- Global controls now use Tailwind 4 syntax and generate cleaner spacing classes
- New Mask Component
- New 3D Transforms Component
- New Shapes Component to allow text to flow around shapes!
- Added caption and author support to Gallery Lightbox
- Added CSV (local or remote) support to Table Component
- Added Google Sheets support to Table Component
- Added Drop Zone support to Table Component
- Added box-shadow colour and opacity controls
- Added support for radial and conical Gradients
- Added support for adding custom HTML attributes to the Container component
- Added volume control to the Audio Component
- Fixed dark mode link colours not being applied in the Text Component
- Navbar folders now show active styling when a child page is active
- Components that require PHP will now prompt to switch page extension from html to php
- Improved CMS Online Editor UI on Mobile devices.
- Online CMS Metadata sidebar is now resizable with an increased maximum width
- CMS output now degrades gracefully when front matter is broken instead of failing
- You can now configure the maximum upload size for the Online Editor and MCP server
- Fixed the Online Editor rich text editor incorrectly encoding YouTube embed code
- Fixed issue when creating new posts in the online CMS
- Upgraded the editor styling engine to reduce CSS conflicts and improve isolation
- Markdown Preview option added to the editor
- Fix white edge lines appearing on dark JPEGs in the edit-mode preview
- Added alt text support for CMS Custom Image resources
- Labels in the Inspector no longer overflow, and the label column is wider
- Fixed Toolbar text disappearing on relaunch
- Fixed resource links incorrectly reverting to page links in the link panel
- Fixed custom theme shadows with periods not rendering in Tailwind v4
- Fixed alt text handling for custom and CMS image types
- Added hover-prefixed variants and mirrored scale options for properties
- Fixed the small border radius token incorrectly duplicating the Default value
- Ensured theme and design system values are consistently available to components
- API: Asset-only changes in shared assets are now detected and will trigger a publish
- API: Added a new requiresPhp key
- API: Resource controls now support accept/exclude MIME type filters
- Numerous other bug fixes and improvements
How to Update to the Beta
While we believe the betas of Elements 3 are very stable, however, we don’t recommend using it on live, mission-critical websites. The Tailwind 4 framework touches most parts of the app, including how webpages render, so please check your sites for layout issues or changes before re-publishing.
To install the beta, launch your current build of Elements and go to Settings/Preferences. Under the Updates section, enable beta updates.
Once beta updates are enabled, go to the Elements menu and select “Check for Updates…”.
How to rollback to a previous build
Should you run into an issues when using a new build of Elements you can always rollback to a previous version via the Release Notes page while you wait for a fix.
Keep the feedback coming
Thanks for being part of Elements and for helping us shape the future of web design on the Mac. Your feedback during the beta has already been hugely valuable and will play a big role in where Elements goes from here!
We’re excited to keep building, refining, and shipping, and we really can’t wait to show you what’s coming next.
Thanks
Team Elements
