Update Services

Where services live

Each service is one Markdown file:

src/content/services/<slug>.md

The file name is the slug. /services/custom-sveltekit reads custom-sveltekit.md.

With Decap CMS

1. Open /admin/.
2. Open Services.
3. Click New Services to add, or click an existing entry to edit.
4. Fill in the fields:
   • Title — the service name.
   • Slug — the URL segment. Must match the file name.
   • Icon — an emoji or short text for the card icon.
   • Order — a number. Lower numbers appear first.
   • Excerpt — short text for the list card.
   • Primary Link — the main call to action.
   • Secondary Link — optional second call to action.
   • Body — the Markdown body shown on the detail page.
5. Save.

Decap writes the file and commits it to the repository.

Code-only edition

Create a new file in src/content/services/, for example my-service.md:

---
title: 'My Service'
slug: 'my-service'
icon: '🧩'
order: 10
excerpt: 'A short description for the card.'
link:
  label: 'Request on Fiverr →'
  href: 'https://www.fiverr.com/...'
---

## What this covers

The body of the service detail page.

Save the file. The list page reads it on the next build or dev reload.

Remove a service

Delete the Markdown file. The list page no longer includes it. The detail route returns 404 for that slug.

What not to edit

Do not edit src/content/services/_index.md from the services collection. That file is the list page config. It is edited from the Services Page Config collection instead.

Next step

Read Update Blog for the blog workflow.