L3 Coaching CMS Start

Use this page as the editor entry point. Open the CMS app, then follow the quick publishing workflow below.

Open the CMS

Open the admin interface to create, edit, and publish content.

Open CMS Admin

Quick Workflow

  • Choose the correct collection before editing.
  • Make one logical change at a time.
  • Preview before publishing.
  • After deleting content, remove links pointing to it.

Full Content Guide

Choose the work area:

This guide is written for Sarah and anyone else editing content in the CMS.

You do not need to code to use this workflow safely.

The key rule is simple: make one clear change, preview it, then publish.

5-Minute Quick Start

  1. Open the CMS at /admin.
  2. Open the collection you need (Pages, Audience Pages, Resources, and so on).
  3. Open the specific item.
  4. Make one logical change only.
  5. Click Save.
  6. Preview the result.
  7. If correct, publish.

If something looks wrong, do not continue editing new items. Fix that issue first.

Short Guides: Most Common Tasks

Use this section when you need to make a quick change and do not want to read the full guide first.

Quick Task Index

  1. Add a testimonial
  2. Add a resource article
  3. Add a download
  4. Update homepage cards
  5. Update start page cards
  6. Update learn page programme cards
  7. Update an audience page
  8. Add a workshop
  9. Add a program
  10. Update a facilitator profile

1) Add a Testimonial

Collection: Testimonials

  1. Open Testimonials.
  2. Click Create New.
  3. Add:
  • author
  • role
  • organisation
  • quote
  • full_quote if needed
  1. Set audience_type correctly.
  2. Set consent_confirmed to true only if approval has been given.
  3. Set featured only if it should appear in featured placements.
  4. Save.
  5. Check the relevant page preview.
  6. Publish.

If the testimonial does not appear, first check consent_confirmed and audience_type.

2) Add a Resource Article

Collection: Resources

  1. Open Resources.
  2. Click Create New.
  3. Add title.
  4. Set audience_type.
  5. Add the body content.
  6. Save.
  7. Confirm where this resource will be linked from.
  8. Publish.

Important: a resource can exist in CMS without appearing on a public listing page unless it is linked from somewhere already built.

3) Add a Download

Collection: Downloads

  1. Open Downloads.
  2. Click Create New.
  3. Add title.
  4. Add fileUrl.
  5. Test fileUrl before publishing.
  6. Set audience_type.
  7. Add body description.
  8. Save.
  9. Publish.

If the file does not open, fix fileUrl before publishing again.

4) Update Homepage Cards

Collection: Pages

Entry: home

  1. Open Pages.
  2. Open the home entry.
  3. Find audience_paths.cards.
  4. Edit the card you need:
  • audience
  • description
  • ctaLabel
  • ctaHref
  • image if used
  1. Save.
  2. Preview the homepage.
  3. Publish.

5) Update Start Page Cards

Collection: Pages

Entry: where-to-start

  1. Open Pages.
  2. Open where-to-start.
  3. Find audience_paths.cards.
  4. Update the card text or CTA.
  5. Save.
  6. Preview /start.
  7. Publish.

6) Update Learn Page Programme Cards

Collection: Pages

Entry: learn

  1. Open Pages.
  2. Open learn.
  3. Find programme_cards_section.cards.
  4. Edit the relevant card fields:
  • heading
  • subheading
  • duration
  • body
  • outcome
  • cta_text
  • cta_url
  1. Save.
  2. Preview the Learn page.
  3. Publish.

7) Update An Audience Page

Collection: Audience Pages

  1. Open Audience Pages.
  2. Open Individuals, Leaders, or Organisations.
  3. Confirm audience_type is correct.
  4. Edit the section you need:
  • featured_areas.areas for major cards
  • focus_areas for supporting cards
  • how_it_works.steps for step-by-step process
  • consultation_cta for final call to action
  1. Save.
  2. Preview the page.
  3. Publish.

8) Add a Workshop

Collection: Workshops

  1. Open Workshops.
  2. Click Create New.
  3. Complete the core fields first:
  • title
  • description
  • duration
  • audiences
  • cta_text
  • cta_link
  1. Add optional detail fields such as:
  • learning_outcomes
  • ideal_for
  • included
  • workshop_days
  • faqs
  1. Save.
  2. Check where this workshop should be linked from.
  3. Publish.

9) Add a Program

Collection: Programs

  1. Open Programs.
  2. Click Create New.
  3. Add:
  • title
  • description
  • program_type
  • audiences
  • cta_text
  • cta_link
  1. Add optional metadata such as duration, format, price, and SEO.
  2. Save.
  3. Confirm where the program will be surfaced.
  4. Publish.

10) Update a Facilitator Profile

Collection: Facilitators

  1. Open Facilitators.
  2. Open the correct profile.
  3. Update:
  • name
  • credentials
  • bio
  • image
  1. Save.
  2. Preview any page using that facilitator.
  3. Publish.

Because facilitator entries can be reused, one change may affect more than one page.

How The Schema Works (Important)

Each CMS collection maps to a folder in the repository.

  • Pages -> src/content/pages
  • Audience Pages -> src/content/audience_pages
  • Testimonials -> src/content/testimonials
  • Facilitators -> src/content/facilitators
  • Programs -> src/content/programs
  • Workshops -> src/content/workshops
  • Resources -> src/content/resources
  • Downloads -> src/content/downloads

Each item has structured frontmatter fields (the schema) plus optional body content.

If you add a field value the page template does not read, it will save in CMS but will not appear on the website.

Dynamic Content Map: What Changes Where

This is the most important section. Use it before editing.

1) Pages collection (live and dynamic)

Used for major routes such as:

  • home (homepage)
  • where-to-start (/start)
  • about, contact, book, privacy
  • learn
  • momentum-12-steps
  • nlp-practitioner-training
  • register-your-interest

Common dynamic blocks inside Pages:

  • audience_paths.cards (cards shown on Home and Start)
  • testimonials.testimonialSlugs (which testimonials are shown)
  • programme_cards_section.cards (Learn page programme cards)
  • cta\_\* fields and seo fields

If you want to change homepage cards, start with home and where-to-start entries in Pages.

2) Audience Pages collection (live and dynamic)

Used for Individuals, Leaders/Executives, and Organisations pages.

Critical field that controls matching:

  • audience_type must be exactly Individuals, Leaders, or Organisations

Key dynamic sections in each audience page:

  • featured_areas.areas
  • focus_areas
  • how_it_works.steps
  • consultation_cta

If audience_type is wrong, content can appear on the wrong audience page or not appear where expected.

3) Testimonials collection (live and dynamic)

Used site-wide in testimonial sections.

Display logic depends on schema fields:

  • consent_confirmed must be true for display
  • audience_type controls filtering by audience pages
  • featured controls homepage-style featured usage

You can control exact testimonial display order on some pages through testimonialSlugs in the related Pages entry.

4) Facilitators collection (live and dynamic)

Used where pages/components reference a facilitator profile (for example Sarah Burrows).

Key fields:

  • name
  • credentials
  • bio
  • image

If a facilitator record is edited, any page referencing that facilitator may update immediately.

5) Programs, Workshops, Resources, Downloads (schema-enabled content libraries)

These collections are fully defined in CMS and can be added/edited now.

Current implementation note:

  • these collections are available in schema and content storage
  • some are not yet auto-listed on a dedicated public index route
  • they can still be used where existing templates reference them or when linked intentionally

For Sarah: you can safely maintain these entries now. If you need a brand new public listing page, request a developer route update.

Which Collection To Edit

Use this map before making any change.

  • Pages: main site pages such as About, Contact, Book, Privacy, and other core routes.
  • Audience Pages: pages targeted to Individuals, Leaders, and Organisations.
  • Programs: structured offer entries and programme metadata.
  • Workshops: workshop entries and long-form workshop schema fields.
  • Resources: article/resource entries.
  • Downloads: downloadable asset entries and links.
  • Testimonials: client quotes and testimonial metadata.
  • Facilitators: facilitator profile content.

If you are unsure where to edit, stop and confirm the collection first. Most publishing mistakes happen from editing the right text in the wrong collection.

Safe Editing Routine (Always Use This)

  1. Open one item.
  2. Confirm the title and slug match what you expect.
  3. Edit only the fields needed for this change.
  4. Save.
  5. Preview on desktop and mobile width.
  6. Check links and CTA buttons.
  7. Publish.
  8. Refresh the live page and verify.

Do not bundle unrelated edits into one publish.

Editing Pages In Detail

When updating a page, work in this order:

  1. Hero fields:
  • hero_heading
  • hero_subheading
  • hero image fields if present
  1. Main section content fields.
  2. CTA fields:
  • cta_text
  • cta_link
  1. SEO fields:
  • seo_title
  • seo_description
  • canonical (if needed)

Field Guidance

  • title: internal and display title. Keep it specific.
  • description: short summary for context and SEO support.
  • seo_title: what search engines and tabs see. Keep concise.
  • seo_description: one clear sentence, no filler.
  • cta_link: must start with / for internal pages, for example /book.
  • cta_text: action-led wording, for example Book a Consultation.

Schema tip: in Pages, many sections are nested objects. If a section is missing visually, check the exact nested key names (for example testimonials.sectionHeading and testimonials.testimonialSlugs).

Collection-Specific Instructions For Dynamic Content

Pages: Add or update dynamic cards and sections

Common tasks:

  1. Homepage card updates:
  • edit audience_paths.cards in home
  1. Start page card updates:
  • edit audience_paths.cards in where-to-start
  1. Learn programme card updates:
  • edit programme_cards_section.cards in learn
  1. Testimonial block updates:
  • edit testimonials.sectionHeading and testimonials.testimonialSlugs in the relevant page

For list items like cards:

  1. Keep headings short and clear.
  2. Check CTA label and CTA link together.
  3. Save and preview after each card change.

Audience Pages: Update page-specific dynamic blocks

For each audience page entry:

  1. Confirm audience_type first.
  2. Edit featured_areas.areas for major capability cards.
  3. Edit focus_areas for additional support cards.
  4. Edit how_it_works.steps for process timeline.
  5. Edit consultation_cta fields for final conversion block.
  6. Save, preview, publish.

Testimonials: Add and control visibility

When creating a testimonial:

  1. Add author and quote.
  2. Set audience_type correctly.
  3. Set consent_confirmed = true only when approved.
  4. Set featured if needed for featured placements.
  5. Save and preview on a page that uses testimonials.

Resources (articles): Add and maintain entries

Schema fields currently used:

  • title
  • audience_type
  • body

Safe add workflow:

  1. Create new resource entry.
  2. Add title and audience_type.
  3. Add body copy.
  4. Save.
  5. Add or verify a link path from a live page if needed.

Downloads: Add and maintain downloadable assets

Schema fields currently used:

  • title
  • fileUrl
  • audience_type
  • body

Safe add workflow:

  1. Create new download entry.
  2. Add title.
  3. Add fileUrl and test the URL directly.
  4. Add audience_type and description body.
  5. Save and verify linked access from the intended page.

Learn page note:

  • Downloads from this collection populate the Learn Resources section automatically.
  • The Learn Articles and Resources sections are all-or-nothing. If either Resources or Downloads has no entries, both sections are hidden.

Programs: Add structured programme entries

Core fields:

  • title
  • description
  • program_type
  • audiences
  • cta_text and cta_link

Optional but useful:

  • duration, format, price, learning_outcome, seo fields

When adding a new program entry, also confirm where it is linked from in Pages or Audience Pages.

Workshops: Add structured workshop entries

Core fields:

  • title
  • description
  • duration
  • cta_text and cta_link
  • audiences

Extended dynamic fields:

  • learning_outcomes
  • ideal_for
  • included
  • workshop_days
  • facilitator_id
  • faqs
  • booking_process

If using workshop_days, ensure day_number values are in logical order.

Adding New Content Types

Add a New Page

  1. Open Pages.
  2. Select Create New.
  3. Add title and description first.
  4. Add hero fields.
  5. Add section content.
  6. Add CTA fields.
  7. Add SEO fields.
  8. Save, preview, publish.

Add a New Resource

  1. Open Resources.
  2. Select Create New.
  3. Add title.
  4. Set audience_type correctly.
  5. Add body content.
  6. Save, preview, publish.

Add a New Download

  1. Open Downloads.
  2. Select Create New.
  3. Add title.
  4. Add fileUrl (double-check this URL).
  5. Set audience_type.
  6. Add body description.
  7. Save, preview, publish.

Add a Testimonial

  1. Open Testimonials.
  2. Select Create New.
  3. Add author, role, organisation (where known).
  4. Add quote and optional full_quote.
  5. Set audience_type.
  6. Set consent_confirmed to true only when consent is confirmed.
  7. Set featured only if it should appear in featured areas.
  8. Save, preview, publish.

Images: Correct Workflow

  1. Use Choose Media from the image field.
  2. Upload to the most relevant folder.
  3. Select the uploaded file in the field.
  4. Add image alt text if the field exists.
  5. Save and preview.

If the image does not appear:

  1. Re-open the item and confirm the field still references the image.
  2. Confirm you selected media from the picker (not pasted a broken path).
  3. Save again and refresh preview.

If still broken, request developer help.

Removing Content Safely

There are two options. Prefer hide/unpublish if content may be needed again.

Option A: Hide Or Unpublish (preferred)

  1. Open the item.
  2. Turn off visible toggles such as featured or published-like settings.
  3. Remove links to that item from other pages.
  4. Save and preview.
  5. Publish.

Option B: Delete Permanently

  1. Open the item.
  2. Select Delete.
  3. Search related pages and remove links pointing to it.
  4. Publish those related page updates immediately.

Important: deleting content without removing links creates broken user journeys.

Before You Publish: Final Checklist

  • You edited the correct collection.
  • You edited the correct schema fields for that collection.
  • Title, heading, and body reflect the same message.
  • CTA text and CTA link match.
  • Internal links use valid paths, for example /contact.
  • No placeholder text remains.
  • SEO title and description are present on key pages.
  • Page layout looks correct on desktop and mobile.

For dynamic list content (cards, FAQs, steps):

  • Item order is intentional.
  • No empty cards/items remain.
  • Any new entry is linked from a live page where required.

Rollback (Undo) Procedure

If a publish goes wrong:

  1. Re-open the same content item immediately.
  2. Revert fields to the previous correct version.
  3. Save.
  4. Publish.
  5. Refresh the live page and verify.

If multiple pages are affected, stop new work and restore those pages first.

Common Errors And Fixes

  • Wrong collection edited:

Fix: copy the corrected text, move to the right collection, then revert the wrong item.

  • Right collection, wrong schema field:

Fix: confirm exact field key names from this guide and move content to the field the page template reads.

  • Broken CTA button:

Fix: correct cta_link to a valid path and republish.

  • Missing testimonial on site:

Fix: check consent_confirmed and featured settings.

  • Download not working:

Fix: replace fileUrl with a valid URL and retest.

Ask A Developer If Any Of These Happen

  • A page returns 404 after publishing.
  • URL structure changes unexpectedly.
  • Visual layout breaks even though fields look correct.
  • Media appears selected in CMS but does not render on site.
  • You need a brand new page route that does not already exist.

This workflow keeps edits clear, safe, and easy to maintain.