Overview of Content Items
Explore content items, how they work, and best practices.
A content item is an individual piece of content created from a content type. It’s the finished instance filled with real data.
If a content type is a cookie cutter, a content item is an individual cookie 🍪
Content Item Example: Blog Post
Field Name | Example API name | Example value |
Blog Post Image | blog_post_image | blog-image.png |
Title | title | How to Use Content Lion |
Intro Paragraph | intro_paragraph | Explore common tricks and tips to using the system |
Body | body | Rich text content, a few paragraphs outlining steps for using |
Blog Author | blog_author | John Smith
Product Education Writer |
Every content item includes all fields defined by the content type in its metadata. In the example below, two Blog Post content items are shown with the same fields.
How to Create a Content Item
Step 1: Go to the Asset Repository
Select a specific asset repository if multiple exist. Then, click on Create
Step 2: Select a Content Type
Selecting a type from the dropdown will open the content asset configuration screen
Step 3: Enter Content Details
Fill in the fields defined by the content type. Fields marked as required must be completed to create the item
Step 4: Save the Content Item
Click Save or Done to create the item as a draft. You can keep editing the item, or return back to continue editing later
Step 5: Add Metadata (optional)
Assign the content item to a publishing channel, or add it to a taxonomy category
Publishing a Draft Asset
When you’re ready to make the content live and available for consumption, you can publish the draft asset. To publish, select the content item and click Publish. You’ll have the option to publish the content immediately (Publish Now) or on a specific schedule (Publish Later). Once published, the item is then visible to Content Lion sites, headless REST APIs, and any delivery channel you select.
Any changes made to a published content item requires republishing
Content Item Creation Best Practices
- You must create the content type first
- Use references instead of duplicating content whenever possible