The basis of all created content is rooted in the document types that you create. Without any defined document types, no way would exist to create the content. Chapter 3 covers the details of creating a document type and how they are constructed. This chapter discusses what it means to structure the document types to create the content tree that you designed in your planning phase, as suggested earlier in this chapter.

Think about how you want the users of the Umbraco backoffice to work with the content tree. Some questions you might ask are:

  • Will I need to have different roles accessing only parts of the content structure?
  • Will restricting the types of content that can be created in certain parts of the content tree be necessary?
  • Should editors have access to the Media library? If so, only parts of it? Should they simply have the ability to upload a file/document on a per-page basis?

The answers to these questions (and more) will determine how you build out your document types. For the purposes of this example, assume that the requirements dictate that you create two different editors — one for standard page content (who will have access to all the content) and one for editing news articles only. This means that the news editor should not be able to add standard content pages to the site. To control this access, you set the allowed child types as appropriate when creating the document type for news articles (covered in Chapter 3).

For the news articles, ...

Get Umbraco User's Guide now with the O’Reilly learning platform.

O’Reilly members experience live online training, plus books, videos, and digital content from nearly 200 publishers.