Home
The Blade Presentation Framework was born out of a desire to separate the data logic of a rendering from its presentation logic. A rendering should only need to worry about how it renders its data – not where or how it got data. This lets the application have simpler renderings and data access, and reuse data code across multiple renderings that need the same data.
Blade's powerful presentation framework allows you to create very DRY, single-responsibility renderings. Focus on presentation code and not data access by coding renderings against interface contracts or ViewModels. Your renderings can be ignorant that Sitecore exists, opening up easily testable renderings. It’s also extensible to handle even complex renderings with multiple data sources without increasing coupling.
Installation
Blade Rendering Lifecycle/Quick Start
Using Razor
Using postback and model binding
Debugging Views
Using Dependency Injection with Blade
Unit Testing