Learn how to add modern glass effects to your website using RapidWeaver Elements. In this video, I’ll show you how to create sleek, glassmorphism-style designs that make your layouts stand out.
The best part? Elements has this effect built right in, so there’s no need for extra add-ons or hidden costs
Whether you’re building a portfolio, a business site, or just experimenting with new styles, glass effects are a great way to bring depth and polish to your design.
I have been adding to certain components, just need to copy and paste to each edge in this case now, now I have one working, will be free, no hidden costs
When you start to dig a little deeper the cost comparison is crazy. Maybe. This chart doesn’t even cover everything Elements can do… and perhaps I now need to add “Glass” to the list
FYI: We’re not here to put down Stacks, it served its purpose well for many years. That said, we strongly feel the future is with Elements. It’s a more modern, streamlined system that offers a far better experience for our users.
I agree with you about not putting down Stacks. It was great for its time. However, Stacks is a very old school approach, and most people are now layering a “foundation” of some sort underneath their stacks, which just makes for an awkward set of things that live on other things. The Elements approach of fully integrating the foundation (Tailwind, et.al.) just makes so much more sense. The fact that Elements is WYSIWYG in a WYSIWYG world and Stacks are WYEDWYG (what you edit determines what you get) is also a huge differential of importance, and 21st century, not 20th.
However, I can’t let you completely off the hook. I don’t believe I can reliably deploy sites until you finish Elements. In particular, you have three real gaps that need closing ASAP. In order of importance:
A real replacement for Styled Text. Whether that be a Typography component that is complete (and probably needs to support embedding, e.g. images), a Markdown component, or what I don’t really care. But this is a big missing element, particularly given the CMS remains in partial beta. It’s also a missing component for those moving from Classic to Elements: you go from Styled Text to what?
Third party components active and supported. All the packaging and other things necessary for third party developers to ship things and keep them up to date seems to be missing. So, for instance, if someone else wanted to ship their own product that replaces that missing Typography/Markdown component, I don’t believe they currently can, right? If they can, then I have to ask why aren’t they? (There are two possible modes of failure here ;~)
The CMS (and especially the add-on populate-via-Internet bit). A lot of us have been tinkering with the CMS, then finding things that stall us out or put us in a cul-de-sac. You put the CMS in your spreadsheet list with a green check, but I’d give it a red X as it’s not ready for deployment.
I think we can deploy a website—many already have. However, the gist of what you said is spot on. For me, the key is especially a replacement for Styled Text and full third-party support. While I fully believe the CMS component will be huge, I don’t consider it part of the core of Elements. Once the bugs are worked out and the feature set becomes more mature, it will likely be considered a must-have.