Skip to content

SEO Blogs#2861

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

SEO Blogs#2861
aishwaripahwa12 wants to merge 19 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 framework fatigue, solo side-project backends, and backend architecture mental models, each with a corresponding cover image and cache entry.

  • The how-to-avoid-framework-fatigue and the-mental-model posts are clean; the previously flagged YAML title issue has been resolved and all author slugs exist.
  • The how-to-build-and-ship-a-side-project-alone post has a truncated sentence in the "Will a unified backend platform lock me in?" FAQ answer that ends mid-thought, and still contains two links to the unpublished /blog/post/baas-vs-custom-backend post (flagged in a prior review).
  • All three posts are correctly marked unlisted: true.

Confidence Score: 4/5

Safe to merge once the truncated sentence is completed; the posts are unlisted so the defect won't reach readers immediately, but it should be fixed before unlisting.

The how-to-build-and-ship-a-side-project-alone post has a sentence that ends mid-thought ("That makes the migration path real instead"), leaving visible broken prose in the FAQ section. The post is currently unlisted, which limits exposure, but the text defect is real and will surface when the post is published.

src/routes/blog/post/how-to-build-and-ship-a-side-project-alone-the-backend-stack-that-works/+page.markdoc

Important Files Changed

Filename Overview
src/routes/blog/post/how-to-avoid-framework-fatigue-when-building-backends/+page.markdoc New SEO blog post on framework fatigue; YAML title is now unquoted (previous quote-escaping issue resolved), author and links look valid, marked unlisted.
src/routes/blog/post/how-to-build-and-ship-a-side-project-alone-the-backend-stack-that-works/+page.markdoc New SEO blog post for solo side projects; contains a truncated sentence in the lock-in FAQ answer, and two links to the still-unpublished /blog/post/baas-vs-custom-backend post (previously flagged).
src/routes/blog/post/the-mental-model-every-developer-needs-for-backend-architecture/+page.markdoc New SEO blog post on backend mental models; internal cross-link points to another post in this PR, author slug exists, no issues found.
.optimize-cache.json Image optimisation cache updated with hashes for the three new cover images; no issues.

Reviews (9): Last reviewed commit: "Add FAQ section on backend architecture" | 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>
@adityaoberai
Copy link
Copy Markdown
Contributor

Authors need updates here

Copy link
Copy Markdown
Contributor

@adityaoberai adityaoberai left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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


[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.

For most projects, the built-in database is everything you need until you have a real scaling problem. At that point, you have the revenue to solve it properly.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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

date: 2026-04-09
cover: /images/blog/the-mental-model-every-developer-needs-for-backend-architecture/cover.png
timeToRead: 5
author: aishwari
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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

aishwaripahwa12 and others added 3 commits May 4, 2026 18:05
Co-authored-by: Aditya Oberai <adityaoberai1@gmail.com>
Co-authored-by: Aditya Oberai <adityaoberai1@gmail.com>
Co-authored-by: Aditya Oberai <adityaoberai1@gmail.com>
Copy link
Copy Markdown
Contributor

@adityaoberai adityaoberai left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approved with comments. Please deal with them before merging

Added a FAQ section to explain backend architecture concepts and best practices.
Not if you choose an open-source one. With a platform like Appwrite, you can self-host the exact same stack on your own infrastructure using Docker if pricing or policies change. That makes the migration path real instead

# Start building your side project with Appwrite

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Truncated sentence in FAQ answer

The answer to "Will a unified backend platform lock me in?" ends mid-sentence: "That makes the migration path real instead" — the thought is cut off before completing. Readers will see dangling text right before the closing CTA section. The missing clause (e.g. "…instead of a hypothetical one." or "…instead of a vendor trap.") needs to be restored.

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.

2 participants