The Episerver Community (formerly Social) API is a collection of extensible services for defining and collecting community-generated content.
This section explains the philosophy, architecture, and fundamental concepts applicable to all features of the Episerver Community API. See also: Get started with Episerver Community API.
Every site has unique needs with regard to the management of user-generated content. Sites differ in how they want to invite feedback, shape that content, and moderate its publication. These needs demand flexibility from a content platform. Unfortunately, the implementation of such features is often forced to conform to the limitations of a platform that is not suited to accommodate them.
The Episerver Community API is attuned to these needs:
The Episerver Community API is composed of several micro-services, and each supports a discrete social capability. You may apply services individually to enhance a website with simple community features. You may also apply services in conjunction with one another to create sophisticated, community-generated content tools.
The Community API's services include:
With explicit boundaries around the platform's features, you can establish flexible relationships between components without corruption of the individual responsibilities of those use cases.
For example, consider the relationship that comments might share with moderation. The moderation of user-generated content is a common use case for a digital community but is not always a requirement. The Episerver Community API lets you compose capabilities as necessary to achieve your goals yet avoid inheriting nonessential overhead.
This is important for a couple of reasons. For one, the platform remains light and flexible without jeopardizing the breadth of possibility in its application. More importantly, this design allows the platform to co-evolve with the needs of implementation partners. In this architecture, the responsibility of each component remains intact; new platform capabilities are additive and incur no alteration of intent.
A product review is a good use case in which the platform may be extended by composing capabilities. Consider the typical components of a review:
A comment, with its inherent hierarchical nature, represents a natural root entity in the definition of a review. By leveraging the data extensibility of the Episerver Community API, a comment may be composed with additional data to complete the use case. For example, it may refer to a series of ratings, purchase dates, and other supporting details. See also: Building product reviews with Episerver Community API.
Last updated: Dec 02, 2016