A quick article about our classic documentation and where to find it.
Rapidly heading towards the future, our platform had to update some sections and features as previously used ones weren’t able to achieve some of the new goals.
Our current edition of the platform brings faster and more modern features, allowing us to continue improving the user experience while giving you the latest technologies.
This resulted in us having documents covering features that might not be accessible to everyone, since they are in the classic part of our platform. So we have decided to split the documentation bases.
Why do we keep classic documents?
This question arises naturally when you run into some feature (like the back office), that is no longer being updated and you can’t even see where it leads you to in the next-gen applications. The explanation is pretty simple: since we have many on-premise users and builders still working on the platform in the previous environment, access to the original documentation should be there for them. Although the new capabilities we offer will bring faster and more sustainable experiences, those builders who want to use the classic features shouldn’t be afraid of being left behind.
A difference in the classic vs next-gen environments would be:
- UI-builder vs Page builder
- Classic action builder vs next-gen action builder (allowing you to create your own action steps)
- Classic back office vs next-gen back office (allowing you to customize your back office fully with the page builder)
Where can I find classic articles?
In our classic documentation segment! Always pay attention to the breadcrumbs that show directories and special warnings communicating that the article you’re currently reading is outdated and describes features in our previous environment.
(You can also find the classic documentation link in the footer of our docs environment)
Although, of course, we can’t leave our users without guidance, it’s worth mentioning that the features of the classic-gen environment will not be updated and we strongly recommend building your applications in the next-gen!