Skip to main content
Skip table of contents

5.0 Quickstart: Developer

Tutorial Outcome

At the completion of this tutorial, you will know how to:

  1. Open a Project

  2. Create a Task

  3. Add a Component

  4. Add a Content Instruction

  5. Add a Repeater Instruction

  6. Add a Child Instruction

  7. Add a Slot Instruction

  8. Use the Component Editor

  9. Tag your Components

These comprise the basics required to get started as a developer.

Before You Start

Before you start this tutorial, it is recommended that you familiarise yourself with the developer concepts. Projects, Tasks, and Components are particularly relevant.

Quickstart

1. Open a Project

Open a Project to get started.

If you only have access to one Project this step isn’t applicable.

User Journey – Opening a Project

See the5.0 Opening a Project user journey for more information.

2. Create a Task

Before you can create Components, you’ll need to create a Task for them.

If a Task already exists you can select it either from the Task Dropdown or from the Task Dashboard.

User Journey – Creating a Task

See the 5.0 Creating a Task user journey for more information.

3. Add a Component

Add a Component so you can start defining content in code.

User Journey - Adding a Component

See the 5.0 Adding a Component user journey for more information.

4. Add a Content Instruction

Add Content Instruction so that content editors can insert Content Entries into your Component.

User Journey - Adding a Content Instruction

See the 5.0 Adding a Component Content Instruction user journey for more information.

5. Add a Repeater Instruction

Add a Repeater Instruction to make a section of the Component repeatable for content editors.

User Journey - Adding a Repeater Instruction

See the 5.0 Adding a Component Child Instruction user journey for more information.

6. Add a Child Instruction

Add a Child Instruction to allow content editors to define a Component in the Page editor based on a list of Content types in a Reference link field.

User Journey - Adding a Child Instruction

See the 5.0 Adding a Component Child Instruction user journey for more information.

7. Add a Slot Instruction

Add a Slot Instruction to allow content editors to define the Component in the Page editor.

User Journey - Adding a Slot Instruction

See the 5.0 Adding a Component Slot Instruction user journey for more information.

8. Explore the Component Editor

Become more familiar with the different tools available in the Component Editor.

User Journey - Explore the Component Editor

See the 5.0 Using the Component Editor user journey for more information.

8. Tag Your Components

Tag your Components so that they’re easier to find in future.

User Journey - Tagging your Components

See the 5.0 Tagging a Component user journey for more information.

Further Reading

More on Components

In this short tutorial, you’ve learned the basics of how to create and edit Components.

  1. See the Component concept to learn more about what Components are in Forrit One.

  2. See the Component user journeys for more information on how to create and edit Components and Component Templates.

Other Topics

See all developer user journeys for information about how to carry out other developer tasks, including:

Picklists

Give content editors a selection of values to choose from when editing a Content Item.

Content Types

Add Content Types as templates for content editors to create Content Entries.

Locales

Add Locales to a Project so that content editors can create different sets of Content Entries that may be used when Pages are retrieved.

These sets of Content Entries usually differ from each other based on a locale’s language or culture, and the set that is retrieved for a Page using the SDK at any one time should be based on runtime locale information.

At least one Locale must be added before content editors can edit Pages.

Variants

A Variant is similar to a Locale in that it allows content editors to create different sets of Content Entries that may be used when Pages are retrieved.

However, while Locales are intended to provide locale-based sets of Content Entries, Variants are intended to provide different sets of Content Entries on any basis.

Routing Manager

The Routing Manager can be used to add routings that can be used by Consumer Applications, such as external redirects and rewrites.

SDK

Learn how to use the SDK to retrieve and use Forrit One content.

  • See how to use the SDK.

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.