Content source for SwiftRiyadh.com. Blogs and events in markdown, auto-deployed on merge.
graph LR
A["✍️ Author"] -->|"Open PR"| B["swiftriyadh/\nwebsite-content"]
B -->|"PR merged"| C["GitHub Action\n(dispatch)"]
C -->|"repository_dispatch"| D["swiftriyadh/\nwebsite"]
D -->|"Auto-detected"| E["Cloudflare Pages\n(build + deploy)"]
E --> F["🌐 SwiftRiyadh.com"]
- Open a PR with your new blog or event markdown
- PR gets reviewed and merged to
main - GitHub Actions sends a
repository_dispatchto the website repo - Website repo pulls the latest content and commits it
- Cloudflare Pages auto-detects the commit and deploys
content/
├── blog/
│ └── ...
│
└── events/
└── ...
---
slug: "post-title"
title: "Post Title"
date: "2026-03-15"
author: "Your Name"
github: "yourusername"
twitter: "yourusername"
tags: ["tag1", "tag2"]
excerpt: "Short description."
cover: "https://example.com/image.jpg"
---
Content goes here...Required: slug, title, date, author, tags
Optional: excerpt (auto-generated from body), github, twitter, cover, readingTime (auto-calculated)
---
slug: "event-name"
title: "Event Name"
date: "2026-04-01"
time: "18:30 - 21:00"
location: "Venue, City"
locationUrl: "https://maps.google.com/..."
speakers:
- name: "Speaker Name"
twitter: "username"
github: "username"
linkedin: "username"
tags: ["tag1", "tag2"]
rsvpLink: "https://example.com/register"
cover: "https://example.com/image.jpg"
---
Event details go here...Required: slug, title, date, time, location, speakers, tags, rsvpLink
Optional: locationUrl, cover, speaker social links (twitter, github, linkedin)
| Tool | Description |
|---|---|
| Content Creator | Create blog posts and events with frontmatter, preview, and export. Supports creating from scratch, importing existing .md files, or pasting raw markdown. |
| AI Skill Generator | Copy a ready-made prompt for your AI assistant so it can write content in the correct format — available for both blog posts and events. |
| Markdown Validator | Paste your markdown and validate that all required frontmatter fields are present before submitting a PR. |
- Create a new branch
- Add your markdown file in
content/blog/orcontent/events/ - Use the Content Creator or write markdown manually following the formats above
- Validate your content with the Markdown Validator
- Open a PR — once merged, it goes live automatically