SEO Blogs

[aishwaripahwa12]

New set of SEO Blogs

[greptile-apps]

Greptile Summary

This PR adds three new SEO-focused blog posts covering backend development best practices: avoiding framework fatigue, shipping solo side projects with a minimal backend stack, and a mental model for backend architecture. All three posts are set to unlisted: true, consistent with other recent SEO content in the repository.

• All three posts use valid layout, author (aishwari), and category fields (best-practices, startup, architecture) with corresponding category pages existing in the repo
• Internal cross-links between posts and to existing posts (/blog/post/avoid-backend-overengineering, /blog/post/backend-mistakes-that-quietly-cost-small-teams-weeks, /blog/post/baas-vs-custom-backend) all resolve correctly
• Cover images for all three posts are included in static/images/blog/ and their hashes are correctly registered in .optimize-cache.json
• The previously flagged YAML double-quote issue in the framework fatigue post title has been resolved — the title now uses an unquoted plain scalar (title: How to avoid "framework fatigue" when building backends), which is valid YAML

Confidence Score: 5/5

This PR is safe to merge — it adds new unlisted blog content with no breaking changes.

All frontmatter fields are valid, categories and author exist, internal links resolve, cover images and cache entries are present, and the previously flagged YAML issue has been addressed. No P0/P1 findings remain.

No files require special attention.

Important Files Changed

Filename	Overview
src/routes/blog/post/how-to-avoid-framework-fatigue-when-building-backends/+page.markdoc	New SEO blog post on avoiding framework fatigue; valid frontmatter, internal links resolve, cover image included
src/routes/blog/post/how-to-build-and-ship-a-side-project-alone-the-backend-stack-that-works/+page.markdoc	New SEO blog post on solo side project backend stack; valid frontmatter with startup category, all links resolve
src/routes/blog/post/the-mental-model-every-developer-needs-for-backend-architecture/+page.markdoc	New SEO blog post on backend architecture mental model; valid frontmatter with architecture category, cross-links to sibling new post
.optimize-cache.json	Image optimization cache updated with hashes for all 3 new cover images
static/images/blog/how-to-avoid-framework-fatigue-when-building-backends/cover.png	New cover image for framework fatigue blog post
static/images/blog/how-to-build-and-ship-a-side-project-alone-the-backend-stack-that-works/cover.png	New cover image for side project blog post
static/images/blog/the-mental-model-every-developer-needs-for-backend-architecture/cover.png	New cover image for mental model blog post

_{Greploops — Automatically fix all review issues by running /greploops in Claude Code. It iterates: fix, push, re-review, repeat until 5/5 confidence.
Use the Greptile plugin for Claude Code to query reviews, search comments, and manage custom context directly from your terminal.}

_{Reviews (3): Last reviewed commit: "Update +page.markdoc" | Re-trigger Greptile}

[adityaoberai]

Authors need updates here

[adityaoberai]

Approving to unblock, let's sort out these changes first, then merge and release

[adityaoberai]

Suggested change

	title: How to build and ship a side project alone (The backend stack that works)
	title: How to build and ship a side project alone

Not sure if the brackets are necessary

[adityaoberai]

It is not document based

[adityaoberai]

Suggested change

	[Appwrite Databases](/docs/products/databases) gives you a document-model database with support for complex queries, relationships, and real-time subscriptions. You build the schema from the console or through the API and query it without writing raw SQL. If you outgrow it or have specific requirements later, you can bring in an external database alongside Appwrite. There's no lock-in.
	[Appwrite Databases](/docs/products/databases) gives you a relational database with support for complex queries, relationships, and real-time subscriptions. You build the schema from the console or through the API and query it without writing raw SQL.

[adityaoberai]

Appwrite scales along with your usage. We don't want to make a case against Appwrite

[adityaoberai]

we'll need to change the authors across these blogs since they're all fairly technical

[adityaoberai]

Suggested change

	- **Relational or document databases:** For structured data you query often. User records, orders, posts. Use this for anything with relationships or filtering requirements.
	- **Databases:** For structured data you query often. User records, orders, posts. Use this for anything with relationships or filtering requirements.