Repository layout (apps/console)

This skill targets the Console app at apps/console in appwrite/appwrite; paths are relative to it. Path mapping from the upstream appwrite/website skills:

Artifact	Path
Blog post	src/content/blog/posts/<slug>.markdoc
Docs page	src/content/docs/{path}/index.markdoc
Changelog entry	src/content/changelog/entries/<YYYY-MM-DD>.markdoc
Cover image	public/images/blog/<slug>/cover.avif (min 1200px wide; run bun run generate:cover-manifest after adding)

Also apply the unslop skill to all user-facing prose.

Blog Writing

Blog structure

Each blog post is a single file at src/content/blog/posts/<slug>.markdoc (e.g. src/content/blog/posts/my-post-slug.markdoc). Every file must start with this frontmatter:

---
layout: post
title: "Full title as a string"
description: One sentence summary of what the post covers.
date: YYYY-MM-DD
cover: /images/blog/<slug>/cover.avif
timeToRead: <number>
author: aditya-oberai
category: product
featured: false
unlisted: true
faqs:
  - question: "A question a reader would actually ask."
    answer: "A direct answer. Markdown links to docs and inline code blocks are allowed."
  - question: "Another question."
    answer: "Another answer."
---

The filename (slug) must match the cover image path: e.g. avoid-backend-overengineering.md maps to /images/blog/avoid-backend-overengineering/cover/cover.avif.

Voice and tone

• Direct and opinionated. State positions clearly. Avoid hedging language like "it depends" without then explaining what it depends on.
• Developer-first. Write for engineers making real decisions. No fluff, no marketing speak.
• Practical over theoretical. Lead with the concrete problem, then the reasoning, then the solution.
• No unnecessary superlatives. Don't call things "amazing" or "powerful", show why they matter.

Post structure pattern