Can anyone explain to me why I would switch from RapidWeaver classic to elements? Especially given that for the foreseeable future it’s not going to match classic in terms of all the various add-ons that are available for example I need my website to be able to communicate with Google Sheets and as far as I know that’s not possible no idea when it might be possible either and I don’t do code so whilst it may be possible to do it this way that will be beyond my abilities. So in a nutshell can anyone explain the benefits of switching?
I’m sure Dan or RM will answer this, but let me give you an independent view.
You don’t switch from Classic to Elements if you’re happy with what you’re using. That said, there is a dynamic going on that you need to be aware of, and that’s that the way of dealing with Web sites is changing. You’re probably aware of the shift from straight HTML to CSS. Well, now we’re seeing “foundations” that sit upon everything that came before it. Bootstrap and Tailwind are two of the most common. These foundations really do all the plumbing while you just install fixtures.
Coupled with that, we’ve had some Stacks makers withdraw from the market due to the fact that what they were doing was essentially competitive with these new wider use foundations. And somewhere in that, some of the Stacks makers have rebelled against RealMac and are essentially making a competitive structure to Classic so as to continue using Stacks (not yet on the market; still in development).
Communicating with Google via Elements has been demonstrated. It’s not really much of a coding exercise, at all. It’s more what you’re used to: putting the right variables in the right place to the right values. If you haven’t yet played with some of the more advanced AI agents, you need to, because this is the fastest way to learn how to do something now; it’s like having your own personal tutor answering specific questions. You just have to get good at asking questions.
As for the contention that Elements won’t match all the things you do with Classic, I’d tend to say the opposite. Because Elements is Tailwind based, there’s already a ton of “add-ons” available. Moreover, it’s not yet clear how many developers will be introducing add-ons in the Elements Marketplace once Elements is locked into version 1.0. You need a chicken to make an egg.
My job in Silicon Valley was, essentially, figuring out what technologies a few years out were going to allow users to do things that they couldn’t currently do. Many of us, including RealMac, identified Tailwind (and Bootstrap) as one of those. With a little study, it really does allow WYSIWIG design, whereas Classic is YGSOTYS (you get something other than you saw). Just as PageMaker opened up page design to a new class of users, so are Tailwind/Bootstrap and by extension, Elements.
4 Likes
I do not see the point to switch to Elements. I use Classic and Foundry 2 (NOT 3, which is catastrophic). A wonderful combination. Now that F is gone and probably Classic, too, in a while, I will now prepare to leave Realmac and use another system.
1 Like
You have been busy tonight dredging threads posting advice to people not to move to Elements based on a short trial of a Beta version.
Perhaps you should give it another go? I doubt that Hype is going to offer anything like the support you get on here.
It depends on what kind of stuff one is working on. Hype is superb for my very graphic heavy needs. I have been working with Rapidweaver Classic for a long time, from the beginning I think (and especially when Elixir Foundry, up to version 2, was along). But Elements feels childish in my opinion, trying to emulate some kind of Foundry or Foundation technique. It feels as if Elements is still in beta. So, now I will leave Realmac at the end of this year. It was a great time and I wish Realmac and its Elements and Classic users all the best and a lot of success. I might pop in and have a look once Elements has reached version 2.0, then being a bit more mature in my opinion.
So I’ve done my first website in Elements now (well almost done) and it is certainly taken me more time than it would’ve to do this in classic. That said it probably is the way of the future so I will persevere with it at this point in time, but I do agree with what other points made above that there are plenty of bugs that I’m finding and maybe it is still beta. It feels a little bit like that and I’m not sure where these add-ons are that some people have mentioned can anyone point me in that direction?
If you search “tailwind css examples” you will see lots of sites including tailwind with components and coding to copy an paste e.g.https://merakiui.com/ there are loads fire and some paid for depending on what you want. Most just copy into custom html component.
1 Like
I’m really enjoying our elements overlord 
hahahahaha
Made 15 sites and very happy with the speed and size
To me - it really is the future
Been making websites since 1996.
Best Wishes to you!
1 Like
OK.. so I go there and find ‘stuff’ and ‘copy code’ which I do.. then in elements finally find HTML component under ‘custom’ but how the heck do I put anything in it…like what I just copied.. in Classic just double click into it and paste… can’t see to do that in elements..?
Go to manual and have a look at videos Dev Diary 15 is a good place to start https://docs.realmacsoftware.com/elements-docs/elements-app/components/custom-components
is this what you are referring to
@johnspannenburg missed the the bit how to reveal the edit area, added video