Skip to content

SEO Blogs#2861

Open
aishwaripahwa12 wants to merge 4 commits intomainfrom
aishwariseoblogs/2
Open

SEO Blogs#2861
aishwaripahwa12 wants to merge 4 commits intomainfrom
aishwariseoblogs/2

Conversation

@aishwaripahwa12
Copy link
Copy Markdown
Contributor

New set of SEO Blogs

@greptile-apps
Copy link
Copy Markdown
Contributor

greptile-apps bot commented Apr 6, 2026

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

aishwaripahwa12 and others added 2 commits April 6, 2026 14:05
…ing-backends/+page.markdoc

Co-authored-by: greptile-apps[bot] <165735046+greptile-apps[bot]@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant