Umbraco is a very simple, highly scalable CMS

Body:

In the past few days, the customer has recommended a CMS system umbraco, hoping to make it a product for a general company website. After studying it, it feels very simple, but it is highly scalable.

Umbraca really only does what CMS should do, so it is simple, but its content definition method makes its scalability very powerful.

The default installation environment of umbraco is a hosting host that has never been used before. If you want to install it on IIS, refer to here. The installation is very simple. For more information, see Li Luping's blog, chinese: umbraco has a lot of articles on its website. You can deduct them slowly. Many valuable websites charge fees. Typical value-added service profit methods. let's take a brief look at his system:

1. Setting (SET)

Stylesheets: defines the styles required for templates, pages, and content.

Templete (Template): defines the displayed template, which is actually the masterpage in Asp.net. One feature is that it can be integrated by level and can be defined.

Scripts: the script file used on the website. For example, it includes jquery by default.

Language: The language used in the custom system;

Dictionary (dictionary): it refers to the dictionary reference table. A reference table is made based on the custom language. For example, if three languages are created, create a dictionary item test here, so there are three input boxes for you to fill in, testing/test/bird language test.

Media types: You can define the types of data you need, such as folders (with many statuses), images, videos, and various resource types required in the system, these types will be used in subsequent media management.

Document types (document type): it can be understood as a form type. It defines a set of placeholders, content items on the Content Page, and uses it with templete, A document type corresponds to multiple templates to display different styles.

2. Permission Architecture

It can be divided into user management system and member user system, that is, users and members ).

2.1. Users (User)

The user defines the function operation permissions. First, let's take a look at the permissions of all actions:

Browse node/edit in canvas/create/send to translation/translate/audit trail/delete/move/copy/sort/permissions/Public Access/rollback/update/publish/send to publish /manage host

The management of users is actually whether users have these permissions. The system initially defines three user types, which are actually the permissions groups.

2.2. Members (member)

The member defines the permission for the content.

Member type (member type): Each member type is defined as a type of person. It can be seen as something similar to Windows roles and mainly controls the visibility of content. some special attributes can be defined for each type, similar to dynamic product attributes in the invoicing.

Member groups (member group): something similar to Windows groups, used to group member.

Members (member): the business account. It must belong to one member type and can belong to zero or multiple member groups.

3. developer-oriented definition

Continue later .........

Release date: