I got ELEMENTS Beta last December and have learned bit by bit through trial and error, the help of this community, the great RM Team and not forgetting @elementsbot - who would!
At my old age I was just a copier and paster type of person, but over last few months I have learned how to do custom HTML, TWIG commands and use third party code (add ons) and modify so it will work in ELEMENTS. This to me has been a great achievement gave me brain ache at times. But as one of my favourite football mangers (Bill Shankley) said “Quitters don’t win and winners don’t quit!” I liken ELEMENTS to deciding whether to go electric or stay with ICE.
So today just to be mischievous I took an old file and converted from RW7 to RW8 to Classic and tried out the latest BETA Import and bingo all my file structures have imported getting rid of a load of bloatware in the process. So a resounding OK to importer but then it hit me. I have just spent 9 months of my time when a tool could have done this instantly and saved me loads of time.
Then I realised that time spent learning ELEMENTS has given me tools that this importer has not so it begs the question is the correct route learn ELEMENTS and rewrite or load and copy and paste an old design into a new format?
I think everyone will have an opinion on this and it depends on you where you are in your journey. The “STACKS” world is entering a new chapter, ELEMENTS is a new chapter and sometimes leaving the old world and entering the new is about change and how as individual we cope with change. As in my whole career I have been described as a change manager, disruptor, leader and sometimes called mad, I love a challenge.
ELEMENTS does not do what stack addons do I see a lot on this site, but equally ELEMENTS does a lot of what stacks doesn’t do too.
So you have an option now learn ELEMENTS from scratch and rewrite or convert and copy and paste.
So @dan the importer can import an old RW7 project thats been “upgraded” to Classic and works as BETA intended so well done!