Druware.Server is a foundation, and a general project covering multiple sub projects. A building block of sorts from which a bunch of other little libraries build from, which when combined help us build entire systems with a very high level of reuse. Rather than create a separate project for each of those libraries, we are referencing all of them from here, though most are in different, related Github Repositories.

Druware.Server Library

Druware.Server on Github

The root library from which almost everything else builds upon, the primary responsibilities here are providing the user authentication and management mechanisms, some general startup tools and additional global helpers, like the MailHelper that exists for providing an application wide model for sending email.

Druware.Server.Controllers Library

Druware.Server.Controllers on Github

While the Druware.Server library provides the classes and elements, the Controllers library implements the default WebAPI / REST controllers for them. They are in their own library so that any one that wishes to use the base classes, but override the controllers with custom implementations is more than welcome to do so within their own platforms.

Druware.Server.Content

Druware.Server.Conent on Github

Extending beyond the basics, the Content library provides a foundation of a content management system that can easily be leveraged into many system designs and implementations. Basic Asset, Article, Document and Product entities are pre built and ready to use.

Druware.Server.Content.Controllers

Druware.Server.Content.Controllers on Github

Much like the Druware.Server.Controllers library provides optional controllers to the Druware.Server library, this does so for the Content library. They are in their own library so that any one that wishes to use the base classes, but override the controllers with custom implementations is more than welcome to do so within their own platforms.