# Opportunity to switch to Elements **URL:** \ **Category:** Elements\ **Created:** [May 20, 2025, 12:29pm UTC](https://forums.realmacsoftware.com/t/opportunity-to-switch-to-elements/47667 "2025-05-20T12:29:45Z")\ **Posts on this page:** 1\ **Showing post:** 2
**Author:** ![ben](https://dub1.discourse-cdn.com/flex005/user_avatar/forums.realmacsoftware.com/ben/32/28488_2.png) [@ben](https://forums.realmacsoftware.com/u/ben)\ **Post date:** [May 21, 2025, 8:48am UTC](https://forums.realmacsoftware.com/t/opportunity-to-switch-to-elements/47667/2 "2025-05-21T08:48:11Z")
Hi @zdenek, Great to hear you’re exploring a switch to **Elements** — I think you’ll find it a real breath of fresh air. The WYSIWYG editor in Elements is truly a game changer, especially if you’re coming from platforms that don’t offer a live editing experience. > [@zdenek](#): > > I started from scratch and my site is multilingual While **multilingual support** isn’t built into Elements _just yet_, it’s something we want to add in the future. In the meantime, you can absolutely create language-specific folders in your project and use **Globals** for shared content sections. Globals let you override not only design settings (colours, backgrounds, etc.) but also **text content** , which means you can tailor the same layout for different languages easily. If it helps, I’d be happy to create a quick demo showing how this can be done 🙂 > [@zdenek](#): > > Fondation, Total CMS, Swatches, SEO, Accordion, RWML base, Columnist, Vegas, Photo Pro base, Page Safe, Seams, HTML 5 video, Elevator, FormSnap base, … That’s quite a stack list — and I can imagine it came with a significant investment over time! The good news is that **many of those features are already built into Elements** , or planned for it. Here’s a quick breakdown: ### **🧱 Feature-by-feature comparison:** - **Foundation** → Elements is built on **Tailwind** , the most popular and modern CSS framework today. It offers everything Foundation does (and more), in a cleaner, more maintainable system. - **TotalCMS** → Our work-in-progress **CMS is built directly into Elements**. It’s a flat-file, markdown-based system that requires no setup. [Watch the Dev Diary previews](https://youtu.be/D3fdoQRlblc) for a glimpse of how it works. Just today we released a [preview of instant search](https://forums.realmacsoftware.com/t/dev-diary-83-search-import-og-tags-the-cms-just-got-smarter/47678). - **Swatches** → I think the need for Swatches is eliminated in Elements. Styling is built right into the component system with a far more intuitive and consistent approach. - **SEO** → Elements includes a suite of SEO tools. If you have specific SEO needs, let us know — we can help guide you on best practices. - **Accordion** → Built-in! We have a modern, flexible [Accordion component](https://www.youtube.com/watch?v=w1pfxSfHN5o) ready to use. - **Columnist** → Tailwind supports native CSS columns. Some users have already created free custom components using this — and we can help you set that up if needed. - **Photo Pro** → Elements includes a powerful **Gallery** component with support for remote/warehoused images — just drop in your images and it handles everything else. - **HTML5 Video** → Elements’ **Video** component supports MP4, YouTube, and Vimeo out of the box. - **FormSnap** → Elements has a robust set of **Form components** built-in. Add fields, configure your SMTP or webhook, and you’re good to go. > [@zdenek](#): > > I’m keen to switch to a more ‘moderne’ tool, but I can see all the work that needs to be done. That’s totally understandable — you’ve clearly put a lot of time and effort into your current setup. But rebuilding in Elements is a great opportunity to modernise your site and consolidate features in a cleaner, more future-proof system. > [@zdenek](#): > > what’s the future of staying with RWC? Will it evolve in parallel with [Elements](https://elementsapp.io/) or not? We’re committed to supporting **RapidWeaver Classic** for the foreseeable future, especially for existing users. That said, we can’t speak to the future of third-party tools like Stacks, which are outside of our control. > [@zdenek](#): > > If I switch to [Elements](https://elementsapp.io/), I suppose that will I be able to built-up my site in the same way as it is now. Elements is a fresh start, built with modern tools — and yes, you’ll find a lot of familiar concepts from Classic. But you’ll also enjoy a more intuitive, flexible experience. Once you get hands-on with the live editor and built-in components, it’s hard to go back. > [@zdenek](#): > > If so, which [Elements](https://elementsapp.io/) formula I should go for? If by “formula” you mean **plan** : - The most popular option is the **Plus** plan. - If you’re building and selling sites to clients, the **Pro** plan is the one to choose. You can view plan details here: [elementsapp.io/#buy-elements](https://elementsapp.io/#buy-elements) > [@zdenek](#): > > Can I ask your opinion by looking at [my site](https://www.zeyn.ch)? From what I can see, **most of it could be recreated in Elements** fairly quickly. The core features are either built-in or in active development. If you have any more questions — big or small — feel free to ask. We’re more than happy to help you make a smooth switch to Elements 🙂 --- _[View the full topic](https://forums.realmacsoftware.com/t/opportunity-to-switch-to-elements/47667)._