Possible online services disruption due to Internet related outage
Building Content Fragment Models
Agencies can have custom content fragment models built for content that needs to be repurposed throughout a website. The following is a walkthrough creating a content fragment model to manage a collection of "Puppy Profiles."
While agencies cannot create or modifiy content fragment models at this time, the steps of creating a new model can help users know the information required by platform administrators to make the process as smooth as possible.
Authoring
Creating a new Content Fragment Model
To gain access to content models, browse to the root of AEM
- Press the tools icon
- Then select "Assets."
Then select the Content Fragment Model Icon (image right).
From here, select the folder for your Agency. If you do not see your agency's folder, please contact DoIT.
Now you are ready to Create a new content model.
Setting up your Content Fragment Model
When creating or editing your content fragment model, you will see an interface that looks similar to this image (left.) You can create your content fragment model using any combination of these properties.
We've built a sample content fragment model shown at the bottom of this page which includes at least one of each of these properties.
The text below includes the details of how these properties were set up.
- Single-line Text:
- Field Label. How the field is labeled in the content fragment (Puppy Name)
- Property Name: how the field will be referenced in content management. No spaces or caps please (puppy-name)
- Placeholder: Enter your puppies Name
- Default Value: will set a value for your entry unless you edit
- Max Length
- Required: Yes
- Description: Enter help text to assist people who may be filling out your content fragment.
- Multi-Line Test
- Field Label: How the field is labeled in the content fragment (Description of your puppy)
- Property Name: how the field will be referenced in content management. No spaces or caps please (puppy-description)
- Default Type
- Plain Text
- Rich Text
- Markdown
- Description: Enter help text to assist people who may be filling out your content fragment.
- Number
- Render as numberfield
- Field Label: How the field is labeled in the content fragment (Age)
- Property Name: how the field will be referenced in content management. No spaces or caps please (puppy-age)
- Placeholder: How old is your puppy
- Type: Integer or Fraction
- Default Value will override any placeholder language you entered.
- Required?
- Description: Enter help text to assist people who may be filling out your content fragment.
- Boolean (Check box)
- Field Text: How the field is labeled in the content fragment (Check here if your puppy loves kisses)
- Property Name: how the field will be referenced in content management. No spaces or caps please (puppy-kiss-indicator)
- Default: leave empty for opt-in. Pre-check for an opt-out.
- Description: Enter help text to assist people who may be filling out your content fragment.
- Date
- Field Label: How the field is labeled in the content fragment (When's your puppy's birthday)
- Property Name: how the field will be referenced in content management. No spaces or caps please (puppy-birth-date)
- Default Value: You can select a default date if you prefer, or leave blank.
- Required: Check if this field is required.
- Description: Enter help text to assist people who may be filling out your content fragment.
- Enumeration: create a pull down selector for your content fragment
- Field Label: How the field is labeled in the content fragment
- Property Name: how the field will be referenced in content management. No spaces or caps please.
- Options: use a comma separated array of values you want in your pull down (boy, girl, I'm not sure)
- Description: Enter help text to assist people who may be filling out your content fragment.
- Tags
- Field Label: How the field is labeled in the content fragment (Puppy qualities)
- Property Name: how the field will be referenced in content management. No spaces or caps please (puppy-quality-tags)
- Required: select if tags are required
- Root Path: point to the folder which contains the relevant tags for your content fragment
- Description: Enter help text to assist people who may be filling out your content fragment.
- Content Reference:
- Content Reference: Choose either a single or multi-selector option for content references.
- Field Label: How the field is labeled in the content fragment (Get an image of your puppy)
- Property Name: how the field will be referenced in content management. No spaces or caps please (puppy-image)
- Placeholder: enter text to describe how to use this field
- Default Value: Point to a default content reference if preferred
- Root Path: You can select a root path to help users find the information they are looking for
- Required: Indicate whether this field is required
- Description: Enter help text to assist people who may be filling out your content fragment.
- Link List: allows you to add multiple links to a content model
- Field Label: How this field will be labeled when authoring a content fragment.
- Property Name: Please Note.... there is only one acceptable name for your link list. Link lists Property Name must be set to "linkList" including the camel-case formatting.
- Description: Enter descriptive help text to assist people filling out your content fragments based on this model.
Please Note:
In addition to the requirement to name your link list "linkList" it is also important to note that you can only have a single Link List in your content fragment models. Content Fragments cannot support multiple link lists at this time.
Also consider that link lists are not designed to support high-volume numbers of items, but rather a small finite list of no more than 10 links.
Example
Here is a screengrab of how the above setup looks as a content fragment model.