Elements 2.0 Beta 1 Now Available

IMPORTANT: Make sure you have the “Check for Beta Updates” option checked in the Settings to get the new Beta :wink:


Hello Weavers,

Today we’re pleased to announce that Elements 2.0 Beta 1 is now available :tada:

This release marks a big step forward for Elements. Most notably, it introduces a brand new API that allows anyone to build components with dynamic dropzones. In practical terms, this unlocks an entirely new class of components, including some of the most requested features like content sliders, tabs, lists and more.

Alongside the new API, Elements 2.0 also ships with four new components, watch the video below for a quick overview of each component (and how to get the Beta).

:backhand_index_pointing_right: Open Sample Project in ElementsRequires Elements 2.0!

There are some significant changes under the hood in this build, including API updates. While we expect existing projects to continue working as normal, we’re taking a cautious approach and releasing this as an opt-in beta for now (more details below).

As always with beta software, please make sure you back up your projects and avoid using this build for any mission-critical websites.

What’s new in 2.0 beta 1 (24050)

  • Added Content Slider Component
  • Added List Component
  • Added Tabs Component
  • Added Markdown Component with a live editor
  • Open-sourced Core Components and internal build tools
  • Added @markdown support to the Elements API
  • API: Added support for Dropzones inside loops (@each)
  • API: Added support for Default collections
  • API: Added support for dropping image resources into the Markdown editor
  • Dropping an image or file into a code area now inserts the file path
  • Added right-click option to Edit Markdown
  • Added right-click option to Edit Custom Component
  • Control-click now works in group views in the Inspector
  • Purchased Packs are now collapsed by default
  • Added SVG Mask option to the Image Component
  • Added List styling options to Typography
  • Added Small Caps option to Typography
  • Added border radius controls to Image Slider Component buttons
  • Menu Component now supports background colour and border radius on items
  • Added numerical colour values to colour strips in the Inspector
  • Added option to set spacing between dropdown menu items
  • Added Elegant Theme
  • Added Neon Theme
  • Added Yarrow Theme
  • YouTube video and playlist URLs are now added correctly via Add Remote Resources
  • Videos in Modals now stop playing when closed
  • Accordion Components can now be nested
  • Added support for overriding the site language attribute on a per-page basis
  • Ensure folders do not have page extensions
  • Dark mode media queries are no longer generated when dark mode is disabled (hat-tip @Doobox)
  • Added UI badge to Dev Components
  • Default option can now be set in the Select Component
  • Moved Elements CMS from the Core Pack into its own pack
  • Moved Form Components from the Core Pack into their own pack
  • Project backup is now set to Every time by default
  • Fixed slider values being cut off by increasing available space
  • Fixed radio component styling issues
  • Fixed transparency issue with Modal overlays
  • Fixed issue with resetting default values on theme spacing
  • Fixed CMS Load More not working when used in a subfolder
  • Added support for linking to products in the Elements Store
  • Added ability to upload support logs directly

How to install Elements 2.0 Beta 1 :hammer_and_wrench:

Open Elements > Settings… and select the Updates tab. At the bottom of the panel you’ll find the Danger Zone section. Enable Check for Beta Updates, then close the Settings window.

Next, go to Elements > Check for Updates…. You’ll be prompted to update your copy of RapidWeaver Elements to the 2.0 beta.

If you need to downgrade at any point, older 1.x builds of Elements are available on the Release Notes page.

Open Source: Core Components

The entire built-in Core Pack is now open-source, along with the internal build tools we use to ship Elements. All Core Components, Themes, and Resources are included.

You can inspect how every Core Component is built, track changes as they happen, and, if you’re code-savvy, contribute improvements back via pull requests. The same tools we use internally are now available to the community.

We’ve also expanded and completed the Documentation for the Elements API, along with adding a detailed section on using the open source components and build tools. We’ve even built an Elements Syntax Highlighting extension for Visual Studio Code :sweat_smile:.

Have fun and report bugs :lady_beetle:

Elements 2.0 is still a work-in-progress. We’ve got more features planned, along with ongoing UI polish and bug fixes. If you run into any issues, please report them on the forum so we can get them addressed in upcoming builds.

Buy Elements Today :star:

If you already own Elements, there’s nothing extra to do. Elements 2.0 is included with your existing licence, along with all future updates released during your active licence period.

New to Elements? You can purchase Elements directly from our website, or try Elements for free and explore it at your own pace. When you’re ready to upgrade, everything is already set up and ready to go.

Thanks :waving_hand:

Thanks for being part of Elements and for helping us shape the future. Your feedback during the beta is hugely valuable and plays a big role in where Elements 2.0 goes from here.

We’re excited to keep building, refining, and shipping, and we can’t wait to show you what’s coming next.

Thanks!
Team Elements

6 Likes

Congrats on the HUGE update @dan and team! LOTS to dig into!

BUT…Not seeing the new themes, though… ? (tried restarting, etc. Still not there)

Cheers!

Hey @miketee, can you double check you’re running Version 2.0.0 beta 1 (24056)?

You can find the version number in the Launch and About window. Thanks!

I’ve taken a quick look at the new tab component.

I suspect it won’t work properly on mobile. It will probably need a suitable responsive version. :confused:

Palm → Face

I was looking for new projects…LOL.

Themes are indeed there.

Put down the fire extinguisher! :stuck_out_tongue:

2 Likes

Thank you! I finally can start my full migration from Classic to Elements. Great product!

1 Like

liking this just playing with it

:rofl: :face_with_open_eyes_and_hand_over_mouth: :tada: :piñata::clap:

@dan I’m not having any luck getting the “@markdown” directive to work. Is there something special I need to do to make it work?

Are you trying to write your own Component? Because that’s really what @markdown is for. I’m not sure we have all the tools yet to work with that API.

If you’re just trying to use Markdown in a site, drag the Markdown Component from the Components panel.

Did you check the @markdown docs?

You need to specify title, like this (you can multiple per component).

@markdown(name: "content", title: "Content")

:backhand_index_pointing_right: Here’s a demo project.

Don’t forget you can also check out our open source Core components to see what we’re doing :wink:

Yes, I copied this from the docs. I suspect it is because I’m working in VS and that I need to use the build tools to build my component. I was also was trying to get the new global properties to work but I guess I first need to create the corresponing config files and then “build” them with the build tools.

Lots to learn.

Yes, I’m trying to use this in a custom component.

I like the Tab Component and have found a use for it in my site!!

USAF Beret Badges

1 Like

To safeguard before I install ca I just zip up the current Elements build (like i do with other Mac apps) and if things go wrong just then revert back to the previous build if needed?

I’ve included a link to a Markdown Custom Component project in the comment above :slight_smile:

You can download previous builds from the Release Notes page :slight_smile:

1 Like

Like it but have you checked mobile? The three tabs fit the page but the images overlap.

I like the idea of tabs and have some ideas I want to try but will wait and make sure Beta is working ok before trying.

Known issue. Not mobile compatible. Site was originally designed before existence of mobile devices. The conversion to Elements was to redo the site as-is, converting from Go Live (original design) to Elements. Part II will be updating each page (200 or so) to responsive design.

@dan Is it possible to give us a sample project with those 4 new components ?

Yes, it’s in the original post above… just below the video :wink: