Domain Driven UI
Domain Driven Design is neither a method nor a technology, it is a culture, a way of thinking about the needs of the customers first and putting an emphasis on their language, understandings and human interactions.
Thus DDD is not just for backend systems, but a semantic domain model also benefits the UI design. Unfortunately these semantics are often lost in translation when transferred to the frontend because the impedance mismatch is too high. Therefore the users that are actually using the system will not profit as much as they could from your design. I will show you a functional approach that allows you to actually reuse your domain types and behaviour with ease by combining CQRS and the Elm architecture with an overall messaging architecture.
No upfront knowledge in DDD, F# or functional programming necessary.