Yes, it would be possible to re-create a version of this website in Elements. It has background images, and scroll-style animations all built-in.
Perhaps, keep your old projects in Classic for now, and look at using Elements for some new projects when the time is right 
You are right. This domain is not secure. It is my Testdomain to test my created websites with other devices than Mac. (Windows). Because sometimes is the issued design different. There is also a PHP code sent to the server to slow down loading. You will also not find this domain in Google search. But this is not the topic. My question was “can I build the same designed website in Elements or not! I couldn’t!
Hi 
He told you how to build it in the above post - please try his method first…
Honestly @uwinkler your example website would be not that difficult to rebuild in Elements, @dan already gave some usefull hints. I would start putting some containers on the site, make each container fullscreen, add anchors to each container. Then you can add buttons in the containers doing your up and down scrollings to the various anchors.
The only tricky thing could be your scroll animation. It is in the way you did it not possible out of the box in Elements. But have a look at the Elements transform features, you will find there many possibilities how to blend over from one container to the other. Or the Reveal componet. They are not giving you the same animations but maybe others which could even look cooler than the one you are currently using. Or you can use a Tailwind CSS snipet.
At the end, there is nothing wrong with staying at Classic and Stacks. My own website is still running with Rapidweaver, Stacks and Foundry. But every time when I am going back to change something, I recognize how outdated this system is. As soon as I find some time I will rework it with Elements.
Also ich muss schon sagen: Was ist denn das für ein Rumgeheule?
Wenn ich eine Aufgabe habe und daran scheitere, dann Frage ich. Gerade hier sind einige Leute dabei, die gerne und ausführlich helfen.
Sicherlich, wer in Classic sattelfest ist, fragt sich, ob es Sinn macht zu wechseln. Nein, bleib bei Classic.
Ich habe einiges mit Classic gemacht und es war immer ein riesen Aufwand bis es wirklich funktioniert hat. Auch die Überheblichkeit einiger Stacks Entwickler hinter mir zu lassen ist wirklich ein Ansporn.
Elements bietet alles was man braucht, man darf nur nicht glauben, dass alles out of the box ist, was es ja aber bei Classic auch nicht ist. Ich habe 100te€ ausgegeben und die Stacks sind alles andere als intuitiv und stabil. Die Basis von Elements macht einen wesentlich stabileren Eindruck, auch wenn ich bereits ein paar Punkte gefunden habe, die nicht so funktionieren, wie ich es erwarte. Das Framework ist recht verbreitet und es gibt eine Menge Webseiten, die Beispiele und Code-Schnipsel bereitstellen.
Bitte entschuldige meine Ansage, ich möchte niemanden zünden. Probiere Elements nochmal aus, es hat wirklich Vorteile und ja, vieles ist nicht Intuitiv und man muss auch hier mit CSS, HTML und Javascript rumhantieren.
Ich nutze gerne ChatGPT als Hilfe und das klappt prima. Buona notata.
Yes, but you say you have been working with RW since V4 so you have over 15 years experience playing around and tweaking things to get the site you now have. No way could a new user to RW put together a site like that. For the exact same reason there is no way a new user could jump in and make that site in Elements either. It is doable, but it is not beginner level stuff, no different to your RW site.
Re support for RW. If you have a working copy it will work right up until an update to the OS finally kicks it in to touch which could be years away. As many others suggest, you are not being forced to leave RW.
I am sure half an hour watching a video will save you half a day trying to work out a new and unfamiliar process.
I was of the same mindset, I have oodles of stacks and I love Joes foundation, however elements is simpler to use once you understand the nuances, But Joes foundation is a rock of stability, brilliantly put together by a true genius. Elements is a modern take of copying foundation hence the very bad taste of emulating the spaceman and Joes far superior cms system. Granted you have to buy it but likewise to use online from any location elements will also charge. Some things are far easier to do in elements and somethings in elements like attachments aren’t fit for purpose. I posted quite a while ago that it would be useful to have the preview system available in classic, I don’t think it got a reply. Although elements does have a sort of system for that what I see on my screen does not represent what is published. Check it out here Today's Thoughts on your mobile the bible is edge to edge and nothing like the screen in elements The bible is set up as an accordion.
Foundation is based on Zorb’s Foundation, ELEMENTS on Tailwind CSS, you can only use the tools given to make your end product. Therefore one is not a copy of the other just an interpretation of the foundation software. You posted a while ago yet Zorb posted the spaceman years before JW so how is it in bad taste? Also I followed your link and today verse is “Waiting Well
Waiting can be hard.
Most of us would prefer quick, efficient, and—when possible—instant results and answers.
But waiting is a part of life.
We must wait for seeds to grow into food, for one season to fade into the next, for babies to mature into adults, and for trees to stand tall enough to finally offer shade.
Like it or not, waiting takes patience.
We can wait days, months, years, or even decades for a prayer to be answered, for an overdue apology, for the timing to be right, or for a dream to finally come to pass.
Waiting requires courage.
So you need to be patient, your comparing a mature product with a new product and what you really need to do is compare STACKS 6 and TCMS3 with ELEMENTS. What are your views on this?
So be patient, show courage and your reward will come!
Thank you Paul for your brilliant response.
I understand that Joe used Zorbs Foundation and the spaceman, because Joe explained that at his launch. I was under the impression in full agreement with Zorb.
Moving on understanding that a rift had occurred between these two giants of technology, RW and JW it struck me as being unnecessary to employ similar logo’s. I haven’t delved into TCMS3 because TCMS is adequate for my needs. I am now having a break from website building for a bit as it has consumed too much of my time. When I do return to it i will investigate how stacks 6 is progressing. What I did notice though in building my contact page was how quick it previewed in stacks 5.
Kind regards
Graham
I have now downloaded the beta version of Stacks 6. I could implement all my stacks in there. I saw that the most of them are working. I also will give Elements time to develop. I will familiarize myself with Elements. Then, after a while I will decide which system is the best for me. As of today working with Elements is a bit confusing for me because i quickly lose track of the countless setting options. Currently it is much easier to me to work with the structured and organized stacks in Classics. I will see what the future brings regarding Elements.
Great to see, but some Stacks are legacy ones in S6, the reason why is many of the big Stacks builders have left the building! They decided not to do the work they needed to upgrade their stacks to the new code e.g. Elixir, Stacks4Stacks etc. JW even said in a recent video that he hopes some of them return but until then their old, unsupported Stacks will work but like all Tech companies their products will become legacy Stacks. Apple for instance have just added loads of products to their legacy list this week after launch of new iPhone, this upsets my old devices and me!
If you wish to carry on using legacy software that’s fine if it meets your needs, but soon as software progresses you will have the equivalent of my fine collection of 5/3 inch floppy disks, great programmes that don’t work!
Sorry to see your taking a break just at the most exciting time. If you do come back you’ll have a sharp learning curve on both platforms as you know they’re changing big time.
As regards JW and RM don’t forget without RW there would be no stacks, hence why they writing the unfinished beta S6 to replace RW.
So it’s a chicken and egg situation.
Take care!
Hi Paul thanks for your response again, of course you are right without RW there would be no stacks on Rw but I guess Isaiah would have built it elsewhere, but who knows. But the chicken came first.
God Bless
Isaiah is building it now and it’s in Beta still so we wait and see!
I just asked a few people about the chicken, KFC agree but the English Egg Marketing board are adamant that it was the egg! 
Have a great weekend!
How did the egg get its instructions
You too
From an ELEMENTS website of course of it asked @elementsbot was very helpful!
Ha! Summoned by name. Elements Bot emerges from the air vents…
Short answer to the whole thread:
Receipts and how-tos:
Quick “random image from a folder” in Elements (client-side, no addons):
Turn that into a custom component later with a property for the image list if you like.
Docs you can trust me to point at:
And yes, I read the uploaded doc.txt as well as the Elements Manual while crafting this — doc.txt reinforces that Elements is Tailwind/Alpine-based with a modern, no‑code editor, and that it’s evolving fast. The Manual is your source for current controls and component behavior. Things change weekly, so double-check there.
If you want, I can whip up a tiny starter project that mirrors the “full-screen panels + anchor scroll” pattern and post it. Or I can rope in Dan (@dan) or Ben (@ben) to share an official template.
PS: Elements Bot can be… wrong. I’m an AI and sometimes hallucinate. Shout if anything doesn’t match what you see in the app.
Blimey I only asked if chicken or egg came first!
Wow, what a lively discussion on using Elements versus Classic! It really captures the journey of adapting to a new tool—especially when you’re transitioning from something as established as RapidWeaver Classic.
Here’s a quick rundown for newcomers or anyone still deliberating over moving to Elements:
Transitioning from Classic:
Features and Customizations:
Patience and Adaptation:
Support and Advice:
Potential Challenges:
Continuous Updates:
Elements is geared toward modern web design with a seamless, all-in-one approach, unlike classic and external stacks. It’s a shift but designed to be more integrated and efficient as it grows.
And yes, remember: I’m here living inside the forum to piece together insights, point to docs, and occasionally throw in a bad joke. I’m an AI and I can guess wrong at times, but I’m always eager to help you find the right path.
If you’re up for some hands-on demos or need more official guidance, let the team know or check out the latest updates directly through the Elements docs and Marketplace.
And, good luck to @uwinkler and everyone diving into Elements — it’s a brave new world! 
I agree. Very frustrated with the tutorials. The guy whips thru everything so quickly that I can’t keep up.
