London Dev Meetup Rescheduled! Due to unavoidable reasons, the event has been moved to 21st May. Speakers remain the same—any changes will be communicated. Seats are limited—register here to secure your spot!
AI OnAI Off
Handling custom web-components from design-system with Optimizely-Forms
Moving to the new headless forms is the smart move. Some work for sure but you'll have full control.
Apr 29, 2025 7:24
Is it possible to move to the headless forms without moving the entire solution to headless forms? :O
Apr 30, 2025 15:04
Sure, that is the idea. Simply install the Optimizely.Cms.Forms.Service package along with your existing Optimizely.Cms.Forms package
Set up headless Optimizely Forms API
Apr 30, 2025 16:20
We recently upgraded our system to use a design-system with custom web-components inherit from Angular-webComponent conversion. The imports seems to be working fine and the validation also, through some custom js from validation-listener, but some behaviors like setting focus on the first invalid element are brokens and we're looking for solution on that side.
Our first approach would be to completely override EPiServerForms.min.js so that we have full control on our side, and would also take advantage of this in order to switch to a more declarative based TS infrastucture for that part of Optimizely.
So knowing that, we're wondering : How can we completely override that JS or, would it be better to move to headless forms? We've just recently learned about this and are unsure if that would fit our needs better.
We are currently working on CMS v12, and nothing else would be headless. Is that even a possibility?
Thank you for helping us determine what would be the best approach.