Please help us by completing this survey

Go to survey
Documentation

Docs / Concepts / sensenet 7.0 components

sensenet 7.0 components

With sensenet we offer a robust but modularized Enterprise Content Management system. The whole product consists of multiple packages that build on each other. Every package has the Services component as a prerequisite, because that is the core layer of sensenet.

This article is meant to help you understand the structure of our components and help you answer the first question that arises when starting to work with sensenet:

Which components should I install?

This is a list of the main components we published so far. To see an expanded, curated list of community components, check out our awesome list!

Core layer and admin UI
Feature packages
Client SDKs

Alternatively you can install sensenet 6.5, which is the previous version of sensenet and contains all the features in a single installation.

Services

The Services component lives in the main repository, as it is the core layer of sensenet. Installing it is mandatory and it is the first step of working with sensenet.

This is the only component you need if you have a web application, and are willing to build your own custom UI (views, controllers, etc.) on top of our Content Repository.

This is what you get if you install Services:

After installing Services, you’ll be able to access the Content Repository through several service entry points like the REST api and WebDav, or open/edit files directly in Microsoft Office.

sensenet Services

WebPages

Install the WebPages component if you need a graphical user interface for browsing the Content Repository and performing the actions available on content items (e.g. CRUD or versioning operations, etc.). Please keep in mind that this package contains only an admin UI, no predefined end-user facing interface.

However you can build pages using the powerful app model and our built-in portlets (building blocks that display content), or create your own portlets. The items in this component are built using ASP.NET WebForms.

sensenet WebPages

JavaScript and TypeScript client

The JavaScript client component lets you work with the sensenet Content Repository (create or manage content, execute queries, etc.) by providing a JavaScript client API for the main content operations.

This library connects to the sensenet REST API, but hides the underlying HTTP requests. You can work with simple load or create Content operations in JavaScript or TypeScript, instead of having to construct ajax requests yourself.

Work with the JS client instead of native JavaScript to boost your productivity and make client-server interaction a lot easier.

sensenet JavaScript client

.Net client

The .Net client component lets you work with the sensenet Content Repository (create or manage content, execute queries, etc.) by providing a C# client API for the main content operations.

This library connects to the sensenet REST API (it is compatible with SN 6.5 and SN 7 too), and hides the underlying HTTP requests. You can work with simple load or create Content operations in C#, instead of having to construct web requests yourself.

Speed up your development process and focus on your business logic (either in a custom import or migration tool, or a rich WPF desktop client)!

sensenet .Net client

Workspaces

The Workspaces component is useful for document management or project-oriented scenarios. It gives you predefined workspace structures and dashboards to help organizing different types of content that are related to a project or a client in a unified environment.

Workflow

Integrating Windows Workflow Foundation (WWF 4.5) into sensenet provides many possibilities for creating content-driven workflows. The Workflow component adds a robust and customizable workflow engine to sensenet.

Notification

Email notification component for the sensenet platform. Lets users subscribe to content changes and receive emails either almost immediately or in an aggregated way periodically about changes in the repository.

Is something missing? See something that needs fixing? Propose a change here.