So.. we really wanna use the new shiny angular, we want to build a Single-Page-Application so we can animate page-transitions, but we still want the CMS to control routes and templates (we have many and they change all the time). We also want the CMS-editor to be in control of the pages content and render unknown rows of dynamic content. How can we remain this level of flexibility while compiling our templates Ahead-Of-Time (AOT). In this walk we will follow the thought- and working process, trial and errors and end up with a working solution. It will be lots of options with pros/cons, some live-coding, tradeoffs and will end up with a GitHub repository for everyone to go home and clone.
Slides:
Speaker:
Filip is a frontend developer from Denmark, focusing on delivering great user-experiences to the end-user – often using Angular. He is the Frontend Manager at IMPACT, delivering large-scale commerce-products to well-known business and consumer brands. Filip is passionate about the web, and cares not only about clean and efficient code, but also about accessibility and performance, in order for the web to be available and accessible for everybody – without sacrificing great design and UX. In his local city of Aarhus, Denmark, Filip initiated an angular user group that has grown to become the biggest in the country. Filip is an active community member, and an experienced public speaker, loving to share knowledge and to mentor fellow developers and entrepreneurs. Filip lives in Aarhus, with his wife and two boys, and fluently speaks English and Danish. #JavaScript
