What is involved in making XAML "better"?

I've talked to a lot of people about how to make XAML "better", and by that, I mean making it easier to read, understand and maintain.

Seeing the " better " principles in the abstract makes sense to most people, but how do you apply them to an existing code base?

My friend Joe had this question,  so we got together on a call to see how to make some changes to one of his apps.

And for the benefit of others, we recorded the conversations:

Part One - Helping Joe make XAML more maintainable

In the first part, we look at:

• Understanding existing inconsistencies
• Creating simple custom controls through inheritance
• Inheriting from an existing control and customizing the content
• Creating a simple User Control
• Applying standardization through styles.

Part Two - Helping Joe write maintainable XAML

In the second part, we focus on:

• Extracting complex nested XAML
• Using services to isolate logic
• Using messaging for simple communication scenarios between different parts of the app

I'd love to know if the is helpful, and if we should make a third part...