Broadening implementation options of a .NET platform by adding a JavaScript SDK - CFS2006

From the creator

For years, we have been a Microsoft-first company. Our web experience platform runs on Windows, our developers are .NET developers, and our customers implement custom web experiences using MVC. With the rise in popularity and capabilities of front-end JavaScript frameworks, we saw an opportunity to give our customers more implementation and UX options. But we faced a challenge -we needed to build a JavaScript API for front-end developers who are unfamiliar with our system and ideologies. We wanted to enable them to harness all the features of our platform without being opinionated about framework specifics or forcing them to change how they code. In this session, I will share the journey of building our JavaScript SDK. Session takeaways: - Insights into the architecture decisions that allow our JavaScript layer to control our .NET layer. - How we designed an implementation workflow to ensure the best developer experience (DX). - What it takes to support multiple front-end frameworks.

Published 2019-05-07 · Watch on YouTube ↗
Availability and playback restrictions are controlled by the original channel.