Intellum has been announcing for some time now that Evolve will receive a complete overhaul of its interface. We’ve now received a more specific email about it. Our staff are understandably wondering whether this overhaul of Evolve will have any impact on the designs (themes) we’ve saved, as well as on any templates we’ve created. Can you provide more details on this? It would be unfortunate if padding/ margins, colors, article styles, or similar elements had to be adjusted again due to the update. I personally can’t imagine this happening since you are “only” adjusting the interface and usability, but I can absolutely understand our team’s concerns.
We’re also interested (and perhaps other forum users are as well) in whether it will be possible to switch between the “legacy version” – meaning the current interface – and the new version at any time, at least during some sort of transition phase.
We’re looking forward to the new update, though we still hope that the focus will remain on optimizing existing components. There has been feedback from other forum users in the past regarding this as well.
Please don’t worry, Lars - the new page builder will be a totally separate interface to the existing one, and will remain that way for some time, until we have gone through feedback and feature additions, and we reach a point where we have a feature-complete new version.
Nothing in your current instance will be affected, changed or need to move over - this is a completely separate area in which you can begin to build. The initial release will be with a basic set of features, and then additional functionality will be added over time, so there is no rush at all to move over to it yet. You can begin to explore it when you are ready.
You can switch between the two as you wish, but you will only see net new content created in the new version as you build it, and not your existing courses.
The new Evolve is meant to work on feedback received over time from current Evolve, and also to optimise everything for speed, simplicity, accessibility, and collaboration, whilst being even easier for new users to get on board. with and reduce the learning curve. We do hope you will try out the new interface at some point and give your feedback in its early stages.
If you have any further questions, please do share.
thank you very much for the quick reply. Now comes an essential question: From your first paragraph, I gather that there will initially be two parallel systems. However, it also sounds like at some point there might only be one interface/page builder. That in itself is not a bad thing.
What I’m wondering about, though, is compatibility. You mentioned that in the new page builder, the existing courses are not visible/available (as far asI understood). Does that mean the current courses are not compatible with the new page builder? I recall there was another overhaul in the past where older courses, from a certain version onwards, were no longer readable by Evolve. Would this eventually be the case here as well?
For now at least, there is no option to import old courses into the new builder. This is a total overhaul of the tool and its code. Until we have feedback from users, further development, and feature parity, there won’t be an option to import, but it’s something that is being considered - how best to approach in the future. Again, this is an area in which feedback and analysis of user needs will be vital to us.
For me, the prospect of an updateable version is a must. We have many customer projects that will be updated over the years. If this is called into question, I see it as a major loss of confidence in your product. Even if certain corrections need to be made (I could understand that) it must remain future-proof.
Do I understand the new builder as a simpler editor for users with less skills? So far, we have opted for evolve because it is so flexible and customizable for us as professionals. Is the full range of functions with all blocks and logics guaranteed?
Thank you for raising these important questions — and for sharing the same concerns that we know many in the community may be wondering about. I’m Emily, the Product Manager for Evolve, and I wanted to respond directly.
Our goal with the upcoming Evolve overhaul is to make the product more approachable and easier to use for all customers, while retaining all of the powerful, highly customizable features that you and your team know and love. Our aim is to get the first version into your hands as soon as possible so we can gather feedback, and we’ll be relying on the community — and engaged users like you — to help us ensure we’re continuing to innovate and deliver real value over time.
With this in mind, we’re rebuilding Evolve from the ground up. This gives us an opportunity to improve usability, performance, and consistency without taking away the flexibility that makes your existing themes, templates, and styles so valuable. While we’re still finalizing migration details, rest assured that the legacy version of Evolve isn’t going away anytime soon — we fully understand that customers have active projects, unique workflows, and historical design work that needs to be preserved during any transition.
Right now, I’m gathering insights from customers to help guide our migration planning and identify what’s most important to consider. If you (or anyone reading this) would like to contribute your perspective, I’d love to hear what aspects of your current setup are most crucial to preserve. You can reach out to me directly or book time with me here — every conversation helps shape the migration approach and can even influence our roadmap.
Thank you again for your thoughtful message — and for being part of this exciting next chapter for Evolve!
