We’re back with another video (yes, already), this is in response to a few comments about Elements looking too complex after yesterday’s Custom Components video.
Hopefully you’ll see that building a website with Elements can be as simple or as complex as you want to make it. If we get the UI and the feature set just right, it’ll allow a nice progression of growth for all users.
Your feedback is really invaluable, do us know what you think of today’s video in the comments below.
Thanks Dan! I like the idea of being able to custom code my own stacks…as demonstrated in episode 22. To build a simple card like you did…using ai to assist in coding the Tailwind…and the final result was no different than using the built in RW tools to build a card WYSIWYG and turning it into a global…just the longer, more complicated road.
I love that the new RW Elements will allow us to do this sort of thing…but I think the average RW user wants to hammer out sites quickly. I play devil’s advocate in my comments so it’s never me putting anything down.
Would it be possible to show us how to build something a little more specialized that is not part of the native tools and that we’d need to custom build?
Thanks! Keep up the great work.
I think the bottom line here is that folks can have the best of both worlds with Elements, a simple to use WYSIWYG program if that is all you need but which gives you access to a powerhouse underneath if you need more.
That surely must be a win-win situation and I look forward (like everyone else) to putting it though it’s paces when you start rolling out the alpha.
One question though - I seem to recall way back when Elements was first being talked about that it was mentioned that it would also run on iPads (presumably M processor ones). Is this still the case or did I imagine this?
Theoretically we could make it run on the iPad, but that’s not on our roadmap. However, we think a better future would be to allow for online editing, that way you can use any — Keep in mind this is a longer term goal, but should give you an idea of the direction we’re heading in.
I believe that changing the name to simply “Elements” would eliminate confusion and complaints. RapidWeaver is a completely different app, and a name change would make it easier to understand the distinction, allowing for a fresh start without the need to explain the differences between RapidWeaver and RapidWeaver Elements.
Yeah meh… the only difference to explain isn’t difficult: Rapidweaver is the thing I play with, Elements is another guy’s thing that I can just watch play with So CTA Elements would be a better name
So CTA Elements would be a better name 