# Apologies for this question **URL:** \ **Category:** RapidWeaver Elements\ **Created:** [July 18, 2024, 10:59am UTC](https://forums.realmacsoftware.com/t/apologies-for-this-question/43760 "2024-07-18T10:59:54Z")\ **Posts on this page:** 9\ **Page:** 1
**Author:** ![Skiddersmusic](https://dub1.discourse-cdn.com/flex005/user_avatar/forums.realmacsoftware.com/skiddersmusic/32/19975_2.png) [@Skiddersmusic](https://forums.realmacsoftware.com/u/Skiddersmusic)\ **Post date:** [July 18, 2024, 10:59am UTC](https://forums.realmacsoftware.com/t/apologies-for-this-question/43760/1 "2024-07-18T10:59:54Z")
I don’t come to the Forum much at all, so apologies for this question that must have been already answered. I had a search and look through first. “Elements” - will that be a replacement for “Classic”? Is it intended to be better? Will there be an upgrade path? Many thanks in advance. ---
**Author:** ![Heroic\_Nonsense](https://dub1.discourse-cdn.com/flex005/user_avatar/forums.realmacsoftware.com/heroic_nonsense/32/20666_2.png) [@Heroic\_Nonsense](https://forums.realmacsoftware.com/u/Heroic_Nonsense)\ **Post date:** [July 18, 2024, 11:44am UTC](https://forums.realmacsoftware.com/t/apologies-for-this-question/43760/2 "2024-07-18T11:44:07Z")
Hi @Skiddersmusic, _Elements_ is a new product, intended to be sold next to _Classic_, so _RapidWeaver Classic_ will still be available and supported. I suggest you watch some of the videos here on this website to see what _Elements_ is about. _Elements_ is not backwards compatible with _RapidWeaver_ _Classic_ (you can’t open projects from one in the other). Pricing is as of yet unknown, and I have no idea if there will be a discount for existing customers. Cheers, Erwin ---
**Author:** ![Flash](https://avatars.discourse-cdn.com/v4/letter/f/f475e1/32.png) [@Flash](https://forums.realmacsoftware.com/u/Flash)\ **Post date:** [July 18, 2024, 2:04pm UTC](https://forums.realmacsoftware.com/t/apologies-for-this-question/43760/3 "2024-07-18T14:04:08Z")
Classic remains a supported application. Most importantly it is the best current solution for/if you are using Stacks. Elements will do much of what Stacks can do, though it will take quite a while for third party developers to create ALL the “unique use” plug-ins Stacks has generated over the years. However nearly all the basic functionality of a CSS Framework is built into Elements right out of the box. Elements is far more flexible and user friendly and is a true WYSIWYG interface. As Erwin suggested, check out the videos on [Realmac’s Youtube channel here](https://www.youtube.com/@realmacsoftware). The first beta build Elements is coming very soon, not announced exactly, but soon. ---
**Author:** ![Skiddersmusic](https://dub1.discourse-cdn.com/flex005/user_avatar/forums.realmacsoftware.com/skiddersmusic/32/19975_2.png) [@Skiddersmusic](https://forums.realmacsoftware.com/u/Skiddersmusic)\ **Post date:** [July 18, 2024, 2:20pm UTC](https://forums.realmacsoftware.com/t/apologies-for-this-question/43760/4 "2024-07-18T14:20:17Z")
Thanks both 👍🏻 ---
**Author:** ![Mathew](https://dub1.discourse-cdn.com/flex005/user_avatar/forums.realmacsoftware.com/mathew/32/2771_2.png) [@Mathew](https://forums.realmacsoftware.com/u/Mathew)\ **Post date:** [July 18, 2024, 3:10pm UTC](https://forums.realmacsoftware.com/t/apologies-for-this-question/43760/5 "2024-07-18T15:10:52Z")
> [@Flash](#): > > Elements will do much of what Stacks can do, though it will take quite a while for third party developers to create ALL the “unique use” plug-ins Stacks has generated over the years. I don’t want you (@Skiddersmusic ) to be fooled by this statement. There are many (perhaps the majority) of current Stack developers that will not be developing Element equivalents to their stacks. So it’s quite possible if you use some specialty stacks that the Elements equivalent will never come to Elements or will come to Elements in 1, 2, or more years. If you are only using default stacks or very standard stacks then you may be in great shape for Elements. ---
**Author:** ![Flash](https://avatars.discourse-cdn.com/v4/letter/f/f475e1/32.png) [@Flash](https://forums.realmacsoftware.com/u/Flash)\ **Post date:** [July 18, 2024, 3:24pm UTC](https://forums.realmacsoftware.com/t/apologies-for-this-question/43760/6 "2024-07-18T15:24:01Z")
> [@Mathew](#): > > There are many (perhaps the majority) of current Stack developers that will not be developing Element equivalents to their stacks. This is true. However there are developers all around the world. Stacks was getting to the point of being saturated with solutions, many multiples with the same basic functionality, albeit, with their own nuances. Elements is a brand new slate. The fact the code is all modern, has allowed Realmac to open up the API (hooks for 3rd parties) to create new tools, replicate the functionality of the many stacks out there, and because of the new capabilities and interface, better than ever before! The future is bright. @Skiddersmusic This may be more than you wanted, but Erwin is right, the players will almost certainly not be the same and it will take time. ---
**Author:** ![Heroic\_Nonsense](https://dub1.discourse-cdn.com/flex005/user_avatar/forums.realmacsoftware.com/heroic_nonsense/32/20666_2.png) [@Heroic\_Nonsense](https://forums.realmacsoftware.com/u/Heroic_Nonsense)\ **Post date:** [July 18, 2024, 6:05pm UTC](https://forums.realmacsoftware.com/t/apologies-for-this-question/43760/7 "2024-07-18T18:05:31Z")
In addition, because _Elements_ is based on Tailwind, all the basic Tailwind based components you can find on the web (mostly free too) will work out of the box in _Elements_ by pasting the code like @dan has shown in the vids. This means that someone can quickly code atoms and components (the basic building blocks as defined in _Elements_) based on pre-existing Tailwind code, after which it really becomes drag-and-drop. For example - don’t like the dropdown atom that comes with _Elements_? **[Here’s](https://flowbite.com/docs/components/dropdowns/)** a free replacement. Need a progress bar? **[Here’s](https://tailwindcomponents.com/component/area-liveability-score)** a free one. Missing a contact form? The Tailwind community has you covered with lots of examples, like **[this one](https://tailwindcomponents.com/component/fully-working-contact-form-for-tailwind-css)**. Tailwind has been around for a while and has a big community of designers and devs building for it. And most of those components will work out of the box with _Elements_ too, by pasting the code into your project. The ones that don’t work like this, because they need additional API hooks, can be made compatible with a little effort. Don’t forget that this is how Stacks started too. Oodles of “button” stacks, “columns” stacks and other basis elements (no pun intended) were the first ones to arrive. Other open source JavaScript or PHP projects were poured into Stacks form (like ratings stacks, comments functionality, contact forms and even complete PHP suites like [Sitelok](https://www.vibralogix.com/sitelokpw/) were Stack-ified). **TL;DR:** In the short term, with a little copy/pasting, you can add Tailwind components to _Elements_. It will take time for people to put this code in predefined components, so it will really be drag-and-drop. Cheers, Erwin ---
**Author:** ![upssjw](https://dub1.discourse-cdn.com/flex005/user_avatar/forums.realmacsoftware.com/upssjw/32/26063_2.png) [@upssjw](https://forums.realmacsoftware.com/u/upssjw)\ **Post date:** [July 18, 2024, 6:16pm UTC](https://forums.realmacsoftware.com/t/apologies-for-this-question/43760/8 "2024-07-18T18:16:59Z")
I asked ChatGPT to write some js to load a different image on every page load, I wrote some tailwind to show the image, should be easy to load into elements. It worked in vscode, was really quick and fairly simple. So options are huge. ---
**Author:** ![dan](https://dub1.discourse-cdn.com/flex005/user_avatar/forums.realmacsoftware.com/dan/32/28516_2.png) [@dan](https://forums.realmacsoftware.com/u/dan)\ **Post date:** [July 19, 2024, 10:34am UTC](https://forums.realmacsoftware.com/t/apologies-for-this-question/43760/9 "2024-07-19T10:34:31Z")
> [@Heroic\_Nonsense](#): > > In addition, because _Elements_ is based on Tailwind, all the basic Tailwind based components you can find on the web (mostly free too) will work out of the box in _Elements_ by pasting the code like @dan has shown in the vids. > > This means that someone can quickly code atoms and components (the basic building blocks as defined in _Elements_) based on pre-existing Tailwind code, after which it really becomes drag-and-drop. > > For example - don’t like the dropdown atom that comes with _Elements_? **[Here’s](https://flowbite.com/docs/components/dropdowns/)** a free replacement. > > Need a progress bar? **[Here’s](https://tailwindcomponents.com/component/area-liveability-score)** a free one. > > Missing a contact form? The Tailwind community has you covered with lots of examples, like **[this one](https://tailwindcomponents.com/component/fully-working-contact-form-for-tailwind-css)**. > > Tailwind has been around for a while and has a big community of designers and devs building for it. And most of those components will work out of the box with _Elements_ too, by pasting the code into your project. > > The ones that don’t work like this, because they need additional API hooks, can be made compatible with a little effort. 100% this 🔥 The custom components in Elements are going to be a game-changer…