Cloud — Edit Content
Now that cloud CMS is set up, you can edit content from any browser, any device.
Editing works exactly the same as local mode — the only difference is that every Save commits to GitHub and triggers an automatic rebuild.
For a full field-by-field reference, see the Content Creation Reference.
Before You Begin
Make sure:
- Cloud CMS is set up (see Cloud — CMS Access)
- You are logged into
https://your-site.com/admin/ - Your site is deployed and live
1. Site Settings
Path in CMS: Site Settings → Site Configuration
File: _data/site.yaml
Controls global information used across your entire site.
What You Can Edit
- Site Name — used in the header and meta tags
- Title — page title for SEO
- Description — meta description for search engines
- URL — your live site address
- Author — site owner name
- Twitter Username — for Twitter Card
- Image, Favicon, Logo — brand assets
- Navigation — menu items and CTA button
- Pricing — Starter and Pro tiers
- FAQ — questions and answers
- Footer — text, buttons, trust badges, links
How to Edit
- Click Site Settings in the sidebar
- Click Site Configuration
- Edit any field
- Click Save
Decap CMS commits the change to GitHub. Your site rebuilds in 30–90 seconds.
2. Home Page
Path in CMS: Pages → Home Page
File: content/index.md
Controls the homepage of your site.
What You Can Edit
- Hero — main headline, buttons, image
- Trusted — trust text and logos
- Intro — section title and description
- Intro Grid 1, 2, 3 — three content blocks
- Stats — number counters
- Journal — link to your journal
- Projects — link to your portfolio
- Testimonial — client quote and photo
How to Edit
- Click Pages → Home Page
- Expand the section you want to edit
- Update the fields
- Click Save
Open https://your-site.com to preview after the rebuild finishes.
3. About Page
Path in CMS: Pages → About Page
File: content/about.md
Controls your About page.
What You Can Edit
- Title, Description, Image, Keywords — metadata
- Author — page author
- Body — full page content in Markdown
How to Edit
- Click Pages → About Page
- Edit metadata fields at the top
- Edit the Body field (Markdown editor)
- Click Save
4. Contact Page
Path in CMS: Pages → Contact Page
File: content/contact.md
Controls your contact form and page.
What You Can Edit
- Title, Description, Image, Keywords — metadata
- Form — action URL, method, submit button text
- Head — kicker, title, description text
- Fields — form fields (name, email, project type, budget, message)
- Note — small note below the form
- Trust — trust badges
How to Edit
- Click Pages → Contact Page
- Edit the metadata
- Expand Form to change the form action
- Expand Fields to add or remove form fields
- Click Save
Note: The form uses Formspree by default. Replace
actionwith your own Formspree endpoint, or another form service.
5. Journal Page
Path in CMS: Pages → Journal
File: content/journal.md
Controls the journal listing page — the page that lists all your blog posts.
What You Can Edit
- Title, Description, Image, Keywords — metadata
- Collection — which collection to list (default:
posts) - Pagination — number of posts per page
- Sort By — sort field (default:
date) - Sort Order —
ascordesc
How to Edit
- Click Pages → Journal
- Edit metadata and pagination
- Click Save
The Journal page does not contain articles. It lists the articles from the Blog Posts collection.
6. Projects Page
Path in CMS: Pages → Projects Page
File: content/projects.md
Controls the projects listing page.
What You Can Edit
- Title, Description, Image, Keywords — metadata
- Collection — which collection to list (default:
projects) - Pagination — number of projects per page
- Sort By — sort field (default:
date) - Sort Order —
ascordesc
How to Edit
- Click Pages → Projects Page
- Edit metadata and pagination
- Click Save
7. Blog Posts
Path in CMS: Blog Posts
Folder: content/posts/
Each blog post is an individual Markdown file.
What You Can Edit
- Title — post title
- Description — short summary
- Image — featured image
- Date — publish date
- Author — author name
- Tags — list of tags
- Body — full article in Markdown
How to Create a New Post
- Click Blog Posts in the sidebar
- Click New Blog Posts at the top
- Fill in the fields
- Write the body
- Click Save
The post is committed to GitHub. It appears on your live site after the rebuild.
How to Edit an Existing Post
- Click Blog Posts
- Click the post title
- Edit the fields
- Click Save
How to Delete a Post
- Open the post
- Click the three-dot menu at the top right
- Click Delete entry
- Confirm
8. Projects
Path in CMS: Projects Collections
Folder: content/projects/
Each project is an individual Markdown file.
What You Can Edit
- Info — short category label (e.g., "Architecture System")
- Title — project name
- Description — short description
- Image — featured image
- Client — client name
- Years — project year
- Date — project date
- Tags — list of tags
- Author — author name
- Body — full project content
How to Create a New Project
- Click Projects Collections in the sidebar
- Click New Projects Collections
- Fill in the fields
- Click Save
How Cloud Saving Works
When you click Save in cloud mode:
- Decap CMS commits the change to your GitHub repository
- Your hosting provider (Cloudflare/Netlify/Vercel) detects the commit
- The site rebuilds automatically
- Your changes go live in 30–90 seconds
You do not need to open a terminal or run any command.
Differences from Local Mode
| Aspect | Local | Cloud |
|---|---|---|
| Where changes are saved | Your computer | GitHub |
| How the site updates | Auto rebuild on dev server | Auto rebuild on host |
| Preview | http://localhost:8000 | https://your-site.com |
| Speed of change | Instant | 30–90 seconds |
Everything else — the CMS interface, fields, collections — is identical.
Related Content Reference
For field-by-field documentation of each page, see:
- Home Page Reference
- About Page Reference
- Contact Page Reference
- Journal Page Reference
- Projects Page Reference
- Projects Collection Reference
- Blog Posts Reference
- Site Settings Reference
What's Next?
Now that you know how to edit content in the cloud, let's learn about media uploads.