As a developer, you are focused on the technical work required for creating and delivering the content to your audience.
Here is how you can achieve your goal with Content.
Step 1: Access developer files
Developer files are the files that you upload from your development environment to the Content subscription through CLI.
- You can access the Developer files from the Developer tab in the main menu under Resources.
- The developer assets list is for your information only. To update a file, you must push the file again from your CLI tools.
Step 2: Access and view API information
To deliver your content and work with content and assets using our REST APIs, you will need their API information. You can view information such as the delivery URL, Authoring URL, and JSON details in the API information screen content, assets, content types, image profiles, taxonomies, and developer files.
- You can access the API information from the respective forms.
- The API information for a list, including search results and filtered lists, is accessed by clicking the API Information icon.
Step 3: Install the CLI tool
You will be uploading and downloading content, assets, and content model artifacts to and from your Content subscription. Content provides you with a CLI tool called wchtools. You can also bulk upload assets, install sample packages, and trigger a publishing job using the developer tool.
- Install the command-line interface (CLI) based utility for working with Content — wchtools.
- Learn to work with the CLI tool — Working with wchtools.
Step 4: Reference individual content fields in web pages or apps
Using the Content API, you can reference individual content fields from a content item in web pages or apps.
Step 5: Reference published assets in webpages or apps
Using the Content API, you can reference published assets in web pages or apps either directly from your asset collection, or a field in a content item stored in your subscription's content collection.
Step 6: Deliver lists of related content through API
- Developers can use the API information for a search or filtered list to deliver lists of related content on a website or APP.
- For example, composers select a category called "Featured" when composing content. A developer can then use the API information for that category and create a list filtered to display only items categorized as Featured.
Step 7: Set up your development environment
Setting up a local development environment helps you to make changes to the code without disrupting the live site or the changes that are made by other team members. You can test and debug your work locally.
Step 8: Add and update layouts (For sites)
- Developers create and manage layouts that determine the design and layout of the content displayed on your website.
- You can map a single page type to multiple layouts.
Step 9: Customize site (Standard subscription)
It is time to move on to more advanced steps. Our Content developer center contains tutorials and documentation to get you started with customizing the Oslo sample.
Article is closed for comments.