All done, check your email for the details!
Haha, it’s okay. We hear you and agree with most of the suggestions 
1 Like
Excellent I have been waiting for detachable editor since July 24 Editor size copy paste
You do get round to these things when the time fits in with your schedule and of course the other improvements
Just need to be patient
Excellent UI, will make workflow suberb
2 Likes
Hi Guys - This is absolutely SUPER and really wonderful to see the flexibility that is incorporated now - especially the ability to work on 2 screens. Thanks for this!
2 Likes
Ok, thank you!
No problem, check your email 
All of the people that are posting on the site must be brilliant web developers. I am a novice web developer and I have been using stacks for a long time and I don’t see this looking anything light stacks and I have been unsuccessful in creating a website with this. Even the people on here who have offered the help have presented stuff that did not work. It seems to me that you still have to be some sort of high-level programmer for this to work.
1 Like
Plus, I’ve noticed that you have Elements on here that I don’t have access to. I bought the pro level subscription and yet I have bare minimum everything. I don’t have a form elements. I don’t have a CSV display element. Nothing. All I can do on here is put a couple of images and maybe a grid. And some text. What none of it has the ease of use as stacks yet. I am very nervous about this transformation because this could be the end of my web development. Especially if something is done to rapid weaver, classic to make stacks require an upgrade that may have an affect on other stacks, such as Foundry stacks
We all have the same access to components, the components you mention above are not included in Elements I have the Pro version as well no form no csv either, I would suggest to understand the future you take a few minutes to read the Roadmap to see what is being planned, considered or in progress or something you would like added or vote on current Roadmap suggestions, just my thought on this question
https://elements.nolt.io/roadmap
Re able to use the software, this takes time to adjust and as at times changes are made which are slightly different than previous versions needs again time to adjust to.
Think there is plenty of help here to assist with using the software more will be available
Menu grid flex text images video containers etc make up most of a webpage the other specialist components will come at sometime
This is beta software so expect things not to work then work then not work
Just my thoughts
1 Like
You can still use Rapidweaver Classic and stacks. Nothing stops you from continuing that route.
However, as with most things tech, that route is destined for deprecation. The reason for stacks was to deal with the complexities of HTML5 using CSS. But there are new players in town for that now, with Tailwind (Elements uses this) and Bootstrap (Bootstrap Studio uses this) being ways of taking the raw CSS coding problem and making it into higher-level blocks that are more easily understood/manipulated.
Foundry stacks try to do the same thing, but frankly I don’t find them very direct, and that’s what Elements and Bootstrap Studio give you: direct design manipulation without getting too deep into the coding.
Thing is, Elements is still in what I’d call alpha (not beta), as it is still not feature complete or even UI locked. You’re probably too early to it if you need pre-built elements to use. We’re only just starting to get peeks at what others are building that you’d likely be using. Give it time.
1 Like
I have over 3000 stacks. And they do so much. This product seems to be like starting over.
I don’t know what the background is of the people who reply, but it seems that you are claiming it’s working fine when it isn’t. Probably because you are some high-level programmer who is adding extra programming to this product because it falls short. I refuse to believe that there is no one out there besides me that feels this way. Perhaps they are worried they will get booted and then be completely stranded.
I used rapid weaver and stacks and I had a website built and published in a day. But, Not with this product. I paid a lot of money for this product. So far, I’ve gotten zero from it. And any support or advice from anyone on this forum has been a complete failure.
You people aren’t just using the product. A lot of you are pulling in programming from other places like Bootstrap.
I wish you guys would’ve worked it out with the guy who made stacks and made your product continue to prosper instead of starting over with nothing and not fulfilling the real need of the product in the first place.
This was a product that was originally designed for people who needed to build websites quickly and easily and professionally. Stacks helped that become possible and more. I can’t get anything accomplished with this program. And anybody who provided any advice hasn’t really said anything that made anything work. Probably just chimed in to feel more intelligent.
I hope you don’t do anything to stop RW classic from working. Because I have a bad feeling about this program.
Having said that, I just want to say I’m not trying to poo all over your work here. But I hope that this product becomes useful and successful as the stacks add on.
I would be satisfied if I could create one successful website the way I did with stacks.
Elements is a different - and imho a far better - app than Rapidweaver. If you’re heavily invested in 3000 stacks I’m guessing you have extensive experience with Rapidweaver so it’s going to require a change of mindset and some time to learn. It IS starting over. If you try to use it like Rapidweaver you’ll continue to be frustrated.
As far as being web experts, I’m definitely not. I have some past experience with RW and Wordpress but I don’t write HTML or CSS. I am a low level programmer who’s written several pieces of software but haven’t written a single line of code in Elements (and frankly have no intention of doing so).
It’s one of the reasons I lament the lack of the built in components from the early betas - but I’m just going to be patient because I know they’re coming.
Maybe being in the beta program wasn’t for you - wait until it’s polished and then decide.
2 Likes
Just on this point, I have zero interest in the politics of what went on but what I can say for certain is the difference between RW and Stack and working in true WYSIWYG in Elements is worth any new learning curve. Elements is so far ahead in this regard it’s in a different universe.
For me, going back to RW feels like the dark ages.
4 Likes
I never said the software was working completely I do report bugs + my mistakes
in this thread my comment
This is beta software so expect things not to work then work then not work
In other comments I have said you should not build a website with the Beta, it is being improved continuously
Reading the Roadmap is key, what will be added
I think just trying some basic stuff might help in the beginning
Even a simple container needs just trial/play as to what it can do and understand how it works, you could just play with the container for a while and understand everything it can do with just text and images, just on its own you could play with container for ages
there are bugs
2 Likes
And they are getting fixed on the regular!!
2 Likes
Thank you for your candid feedback — we totally understand where you’re coming from. Elements is quite different from the older RapidWeaver and Stacks approach, and that can take a bit of adjustment.
As others have mentioned, Elements is still under active development and not yet finished. Once we introduce the built-in Templates feature, I think you’ll find it much easier to build websites with Elements. That said, this feature (and many others) aren’t quite ready yet, so I understand it might not meet your needs at the moment.
Would you like a refund on Elements for now? You could always revisit it later this year when we launch version 1.0
Thanks again for sharing your thoughts, and please let me know how you’d like to proceed!
1 Like
@dan
I saved a workspace, but when I try to select it crashes. Tried after starting a new project, but it crashes as well.
@Bill Did you submit the crash report to us?
@dan - Just submitted a crash report.