Contribute

Write for Kubesimplify

Join 61+ contributors publishing in-depth, practitioner-led technical writing on Kubernetes, AI infrastructure, and cloud-native.

Why contribute here

  • ✓ You keep the byline, the canonical URL, and the SEO value.
  • ✓ Your post ships with rich schema.org metadata (author + topic + reading time).
  • ✓ We promote it across our YouTube, X, LinkedIn, and Substack channels.
  • ✓ Open source. Edit history is public. Easy to update later.
  • ✓ Free static hosting, instant load, no platform lock-in.

How it works

  1. 1

    Fork the repo

    Fork kubesimplify/website on GitHub. All blog content lives in content/blog/.

  2. 2

    Add yourself as an author

    Edit content/authors.json and add an entry with your handle, name, bio, avatar, and social links. Drop your avatar in public/img/authors/<your-handle>.jpg.

  3. 3

    Write your post

    Create content/blog/your-post-slug.md with the frontmatter shown below. Markdown supports code fences, tables, embedded images, GitHub-flavored extensions.

  4. 4

    Drop your images locally

    Put any post images in public/img/blog/<your-slug>/ and reference them as /img/blog/<your-slug>/file.png. Cover image goes in the same place.

  5. 5

    Preview locally (optional)

    Run npm install && npm run build && npx serve out to see your post rendered exactly as it will ship.

  6. 6

    Open a pull request

    Push to your fork and open a PR. We review for fit and clarity, never to gatekeep voice or perspective. Once merged, it's live within minutes via auto-deploy.

Post frontmatter template

Copy this into the top of your .md file. Required fields are the first six.

---
title: "Your post title"
seoTitle: "SEO-optimized version of the title"
seoDescription: "1-2 sentence summary used as meta description (max 160 chars)."
datePublished: 2026-05-20T10:00:00.000Z
slug: your-post-slug-kebab-case
author: your-handle              # see content/authors.json
cover: /img/blog/your-slug/cover.png
tags: ["kubernetes", "devops"]
---

Your post content in Markdown. Code fences with language tags work great:

```bash
kubectl get pods -A
```

Embed images by dropping them in public/img/blog/<slug>/ and linking:

![Diagram alt text](/img/blog/your-slug/diagram.png)

What we look for

  • Show, don't summarize. Real code, real commands, real outputs. Diagrams and screenshots where they help.
  • Practitioner voice. What did you try? What broke? What does the docs not tell you? That's the gold.
  • Stable URLs. Pick a slug you'll be happy with five years from now. We never break slugs after publish.
  • One topic per post. Better to ship two focused posts than one sprawling 8000-word essay.
  • Original work or a fresh angle. Cross-posts from your own blog welcome with canonical pointing to wherever you published first.

Ready to ship?

Open a pull request and we'll get back to you within a few days.

Browse existing postsFork the repoPitch an idea first