Writing descriptions for your pathways

In this article:

• Overview
• Structure your description
• Example description
• Things to keep in mind
• Who can do this

Overview

A good Pathway description tells learners what they'll get out of a Pathway before they start. The description area is free text, so you can add whatever you like — paragraphs, bullet points and line dividers — and a little structure goes a long way towards keeping it clear and engaging.

Structure your description

A simple, scannable structure works best. A common pattern is:

• What you'll learn — the key outcomes or skills the Pathway covers.
• Requirements — anything a learner should know or have before starting.
• Who this is for — the audience the Pathway is aimed at.

You don't have to follow this exactly — adapt it to your content. The aim is to help learners quickly decide whether the Pathway is right for them.

Example description

Below is an example you can reference. Depending on your content, a similar structure may work well for you.

What you'll learn

• The essential concepts of operating systems
• How to get started with BASH and become confident in the terminal
• What APIs do, why they exist, and the many benefits of using them
• How to manage your code in a repository with Git
• The basics of web application security, testing your code, and clean-code habits
• How to build a web app using the latest React JS syntax
• How to apply basic state management in a React app using Redux
• All about Node and creating a simple REST API
• How to get started with TypeScript — the basics, its features and workflows

Requirements

• Some prior knowledge of computer programming is beneficial
• A willingness to learn a lot of new material

Who this is for

• Anyone wanting their first role as a full-stack developer
• Developers looking to move into a full-stack role or upskill
• Anyone curious about what developers talk about day to day

Things to keep in mind

• The description area is free text — you can format it with bullet points, headings and line dividers.
• Keep it concise and scannable; learners often decide whether to start a Pathway from the description alone.

Who can do this

This is general guidance for anyone authoring Pathways. Editing a Pathway's description is available to Owners, Admins, Managers, Content Managers and Instructors. People Managers, Employees, Members, Volunteers and Restricted users have read-only access to Pathways and cannot.

Updated on: 24/07/2026