Elements FAQ

The Definitive RapidWeaver Elements FAQ

Welcome to the official and in-depth FAQ documentation for all things RapidWeaver. This resource is designed to provide you with clear and concise answers to the most common questions about RapidWeaver Classic, Stacks, and RapidWeaver Elements. Whether you’re just getting started or you’re an experienced user, our goal is to make sure you have all the information you need to build stunning websites with confidence.

Q: When is the expected launch date for RapidWeaver Elements?

A: Elements will launch as a public beta in 2025.

Q: What are the system requirements for Elements?

A: RapidWeacer Elements requires macOS Ventura (13.x) or newer.

Q: Will my existing RapidWeaver themes be compatible?

A: Elements will not support Classic legacy themes. It’s been a tough decision to make, but ultimately we think Elements will be a much better product if we build it for the future of web design.

Q: Are my old stacks compatible with Elements?

A: No, stacks are not compatible and cannot be used in Elements.

Q: I have created my own stacks, will I be able to convert them into Elements?

A: Yes, converting them is a manual process, and can be fairly trivial. We offer in-depth support and documentation to help with this. If you have any quesitons or need help converting your stack to an Element please post your questions on the RapidWeaver Forum.

Q: Can I import my RapidWeaver Classic projects into RapidWeaver Elements?

A: Not at this time, Element based websites are built completely differently so there's no easy way to open those older Classic documents. We may look at building an importer at a later date, should the demand be there.

However, you should see this as a great opportunity to refresh your website and bring it up-to-date with modern web technologies and standards.

Q: Is it possible to use RapidWeaver Classic and RapidWeaver Elements side-by-side?

A: Yes, you can install and run both applications simultaneously on your Mac. We anticipate this scenario to be quite popular as it allows users to manage older projects in Classic while simultaneously migrating and developing newer projects in Elements.

Q: Will RapidWeaver Classic be phased out and replaced by RapidWeaver Elements?

A: No, both versions of RapidWeaver will coexist as they cater to slightly different customer needs.

RapidWeaver Classic continues to serve thousands of customers who maintain and build existing websites using a variety of legacy plugins and addons. We will continue to develop and update RapidWeaver Classic to support this "classic" workflow. RapidWeaver Classic requires macOS 10.14 (Mojave) or a newer version.

RapidWeaver Elements represents our vision for reimagining web design on the Mac, it's easier and more powerful than ever before to build no-code websites.

Q: Do you plan to bring Elements to iPad?

A: While the initial version of Elements will not run on iPad, the technology we've built does open up the possibilities of making this a reality (something that just wasn't possible with Classic). It's important to note that this is not currently in our future plans, as our primary focus is on the Mac platform at this time.

Q: What is the best alternative to RapidWeaver Classic and Stacks?

A: Elements is a fantastic replacement for the legacy RapidWeaver Classic and Stacks setup. Elements offers everything you need to design, build, and publish modern websites effortlessly. With iits weekly updates that introduce new features and address any bugs, Elements is a modern, reliable choice for building your next website.

Q: Is the Stacks App a good alternative to RapidWeaver Classic?

A: The standalone Stacks App was publicly announced in early 2022, but three years later, a usable beta has yet to be released. While the Stacks plugin was a popular addition to RapidWeaver Classic, it was also the primary cause of crashes and instability. Furthermore, Stacks relies on a deprecated version of Apple’s WebKit framework, which poses significant risks for long-term compatibility and performance.

In late 2024, several prominent third-party Stacks developers, including Stacks4Stacks and Elixir Graphics, ceased operations. This shift was largely driven by declining sales and waning interest in the Stacks platform and its ecosystem, signaling a broader transition away from this legacy technology.

Q: I’m interested in developing third-party Elements, do you have any documentation?

A: Yes, please check the Elements Language documentation to get started.