Content Types


By convention content types names should be singular. For example, a content type representing articles should be title "Article". Entering the title "Article" will also fill in the name "article". What's the difference?

  • Title - User-facing identifier for your content type
  • Name - API identifier for your content type (getArticle, createArticle, updateArticle, etc)


Content modeling is done by drag and drop:

Simply drag the appropriate widgets from the palette on the left to the form on the right. The underlying data type of each field is inferred from the widgets you choose. 

Best Practices

  • Put your identifying fields first. Field order is important because it informs how TakeShape generates previews of your content for list views, relationships and taxonomies. Examples of identifying fields are "Title", "Name", "Headline", etc.
  • Make at least one field required.  


In TakeShape content modeling is meant to be as open-ended as possible, that said you create your content types to fulfill a specific use case. Annotations are the way to describe how your content type will be used. There are three possible values for this annotation:

  • Single - Denotes a single item or singleton in programming terminology. E.g. Homepage, Navigation, Menu, Settings 
  • Multiple -  Denotes multiple items. This is the default, most of your content types will use this annotation.  E.g. Articles, Products, People, Places
  • Taxonomy - Denotes a content type which is uses to organize others. E.g. Authors, Tags, Categories, Topics


Annotating a content type as a "Taxonomy" allows the relationships between content entires to be surfaced to users when filtering in the asset views and entry list views.

Taxonomies appear in the sidebar in their own section under "Multiple' content types.

A good taxonomy is something you'll use to classify other thing. Tags, Categories, Topics, Subjects, Genres, and even Authors. Right now the way a taxonomy is used in the UI is to help filter lists.

A taxonomy is effectively a multiple content type that we treat slightly differently on the backend. You can switch a multiple content type to a taxonomy and vice-versa at will.

Taxonomies treat their first text field as their “term” field. This is what will be used for auto suggest.

Join us

Interested in joining the team as coworker or investor?