Top 20 NuGet Packages depending on Owin Framework Pages Core

Contains build engine plugins that allow the application to define endpoints that respond to RESTful requests

Provides build engines that can be plugged into the fluent builder to enable your website to respond to requests by returning pages of Html

Contains packages that can be plugged into your application to provide commonly required functionallity like menus, tabs, login, data entry, text editing etc

Middleware that shows the internal structure of pages to help with debugging issues with page composition and data provisioning

Mock implementations of interfaces in the pages core. You can use these to mock the pages package in your unit tests

Default implementations of core interfaces that most people will choose to use. You can implement these framework classes yourself if you want to completely define how the this framework works under the hood, but this is a very advanced use case

Provides a UI for editing pages, layouts, regions etc within the CMS. You can include this in your website to allow the pages to be modified, or you can build a separate website (intranet) for managing website content

You must include this package in your website to render pages defined within the CMS