RapidWeaver Elements 2.1 Now Available

Hi Weavers,

We’re thrilled to announce that RapidWeaver Elements 2.1 is now available!

This release introduces a new Date Picker to the Form Component set, bringing the total number of built-in components to a mind-blowing 47 :exploding_head:

We’ve also completely refreshed the New Projects window. You can now see all of your installed Store projects alongside projects available in the Store. Even better, a number of free projects are now available, making it easier than ever to get started with new designs and ideas, with more on the way soon.

What’s New in Elements 2.1

  • Added Date Picker Component
  • Added New Projects Window
  • Fixed an issue when using the “Duplicate Without Content” option
  • Fixed CSS Classes field test overlaying responsive dot
  • CMS Collection RSS and Sitemap URLs now use absolute URLs

Availability

RapidWeaver Elements 2.1 is available now as a free upgrade for everyone with an active subscription.

If you already own Elements, there’s nothing you need to do. Version 2.x is included with your current licence, along with all updates released during your active licence period.

Crossgrade to Elements

Not using Elements yet? Get 25% off when you crossgrade from Blocs, Sitely, or any other Mac-based website builder. The offer also applies to RapidWeaver Classic and Stacks users. Feel free to share the link below, it automatically applies the discount at checkout.

:backhand_index_pointing_right: Get 25% off Elements for macOS today

System Requirements

In order to run Elements you will need to meet the minimum requirements:

  • Requires macOS 13 Ventura or newer.
  • Apple Silicon or Intel based Mac.

The trial mode in Elements has the following limitations:

  • No publishing: You can’t upload or publish sites in trial mode.
  • No export: Exporting project files is disabled.
  • Maximum of 3 pages: You can only add up to three pages per project.

:backhand_index_pointing_right: Download Elements 2.0.1 for macOS

The Future of Web Design

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 been hugely valuable and played 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

3 Likes

Hi @dan is this 2.1 or 2.01?

I have 2.01, and it is not telling me that I am up to date.

Plus your post has conflicting info:

Check again, it should now be available, and I’ve fixed the typo :sweat_smile:

Very nice…

Will ‘new’ purchases like multithemes get into the projects page?

Great to see the improvements…

1 Like

Unfortunately not. We don’t have control over projects that are distributed independently, so they won’t appear in the New Projects window. Only themes that are published through the Elements Store or Cloud will show up there. It works in a similar way to platforms like the App Store or Steam.

That said, we absolutely want the community to be able to share their work. Support for free community-built themes, components, and other resources is something we’re actively planning. The goal is to make it easy for people to share projects and ideas with the wider Elements community.

What we’re still figuring out is the best way to handle distribution and quality control so that everything integrates nicely with Elements and remains a good experience for users.

So while only Store and Cloud themes appear in the New Projects window today, broader community sharing is definitely part of the plan. I just don’t have a specific timeframe for that yet.

Hi @dan I’m very sorry about this :cry: , but those projects exist by mutual agreement., since you supported the release of free projects promoting the transition from Classic to Elements, I’d like to know if those projects are still useful today.

Thank you.

I don’t understand…

Couldn’t the devs be given ‘tokens’ for those that have already bought?

The end user could then use the tokens for their previous purchases…

Then the dev could put it on the store and then the end user would have access to them?

Just brainstorming… what I’m saying may not be possible…

@dan thanx for all that you do and the patience to answer questions :slight_smile:

I think this would be a waste of time and engineering effort, when we have more pressing features to implement.

The projects users have purchased from third-parties still work, they just won’t appear in the New Projects window, this is exactly how it works in Classic.

I’d say they are still useful, and it’s great that you’ve created both free and paid projects for Elements.

As you know, Elements is evolving quickly, and we’re doing our best to focus development on the areas that will help grow the Elements user base and turn it into a sustainable product.

Your projects have been helpful in supporting the transition from Classic to Elements, and we really appreciate the effort you’ve put into creating them and supporting the community.