SEO Blogs

[aishwaripahwa12]

Four new SEO blogs covering backend strategy, modern tech stacks, open-source development, and self-serve compliance.

Summary by CodeRabbit

• Documentation
  • Added four new blog posts: guidance on backend choices for multi‑client projects; how modern developers evaluate tech stacks; how open‑source developers use Appwrite; and expectations for self‑serve compliance in 2026.
• Chores
  • Extended the image cache to include cover images for the new posts.

[coderabbitai]

Note

Reviews paused

It looks like this branch is under active development. To avoid overwhelming you with review comments due to an influx of new commits, CodeRabbit has automatically paused this review. You can configure this behavior by changing the reviews.auto_review.auto_pause_after_reviewed_commits setting.

Use the following commands to manage reviews:

• @coderabbitai resume to resume automatic reviews.
• @coderabbitai review to trigger a single review.

Use the checkboxes below for quick actions:

• ▶️ Resume reviews
• 🔍 Trigger review

Walkthrough

This pull request adds four new Markdoc blog posts at src/routes/blog/post/*/+page.markdoc (each with frontmatter: layout, title, description, date, cover image, timeToRead, author, category, and visibility flags) and updates .optimize-cache.json with four new cover image entries mapping image paths to hashes. No application logic, exported/public API declarations, deletions, or modifications to existing keys are present.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~12 minutes

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Title check	❓ Inconclusive	The title 'SEO Blogs' is vague and generic, failing to convey meaningful information about the specific content added to the pull request.	Consider a more descriptive title that specifies the primary focus, such as 'Add four new SEO blog posts on backend strategy, tech stacks, and compliance' or similar that highlights the main changes.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch fournewseoblogs

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[greptile-apps]

Greptile Summary

This PR adds four new SEO-focused blog posts covering backend strategy for multi-client teams, modern tech stack selection, open-source usage of Appwrite, and self-serve compliance expectations in 2026. Each post is accompanied by a cover image and a corresponding .optimize-cache.json hash entry.

• All four posts use the valid aishwari author slug, well-established categories (startup, product, open-source, security), and the unlisted: true flag consistent with other SEO posts in the repository.
• Cover image paths in the frontmatter correctly match the static/images/blog/…/cover.png files added in the PR.
• Two minor style issues were found: a double space in how-modern-developers-choose-tech-stacks-today and an inconsistent heading capitalisation (# What Is …) in self-serve-compliance-what-teams-expect-in-2026.

Confidence Score: 5/5

• This PR is safe to merge; it adds only new content files with no functional code changes.
• All four blog posts are well-formed Markdoc files with valid metadata, existing author/category values, and matching cover images. The only issues found are two cosmetic style nits (a double space and a capitalisation inconsistency) that have no impact on rendering or functionality.
• No files require special attention.

Important Files Changed

Filename	Overview
src/routes/blog/post/choosing-a-backend-when-you-manage-multiple-client-projects/+page.markdoc	New SEO blog post about backend selection for multi-client teams; well-structured, valid author/category, unlisted flag is consistent with other SEO posts in the repo.
src/routes/blog/post/how-modern-developers-choose-tech-stacks-today/+page.markdoc	New SEO blog post on modern tech stack selection; contains a double space in the closing paragraph ("messaging, one platform").
src/routes/blog/post/how-open-source-developers-use-appwrite/+page.markdoc	New SEO blog post on how open-source developers use Appwrite; well-structured with valid metadata and consistent formatting.
src/routes/blog/post/self-serve-compliance-what-teams-expect-in-2026/+page.markdoc	New SEO blog post on self-serve compliance; contains a minor heading capitalization inconsistency ("# What Is self-serve compliance?" vs sentence case used everywhere else).
.optimize-cache.json	Cache file updated with hashes for the four new cover images, correctly sorted alphabetically alongside existing entries.

_{Reviews (1): Last reviewed commit: "new seo blogs" | Re-trigger Greptile}

[coderabbitai]

Actionable comments posted: 2

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Inline comments:
In
`@src/routes/blog/post/how-modern-developers-choose-tech-stacks-today/`+page.markdoc:
- Line 139: The sentence contains a double space after the comma in the phrase
"messaging,  one platform"; edit the Markdoc content and normalize the spacing
to a single space so it reads "messaging, one platform" (locate the string
"messaging,  one platform" in the +page.markdoc content and replace the double
space with a single space).

In `@src/routes/blog/post/how-open-source-developers-use-appwrite/`+page.markdoc:
- Line 20: Update the two factual statements in the Markdoc page: change the
license phrase "MIT-licensed" to "BSD 3-Clause License" in the sentence that
currently reads "The entire codebase is MIT-licensed...", and update the star
count phrase (around line referencing "over 46,000 stars") to reflect the
current value by replacing it with "approximately 55.3k stars as of March 2026";
ensure the wording and tense match the surrounding sentences and run a quick
spell/grammar check after editing.

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 0ab4d3f2-784f-44c3-b036-0d4c334d23fd

📥 Commits

Reviewing files that changed from the base of the PR and between 94418f2 and 65ffaa7.

⛔ Files ignored due to path filters (4)

• static/images/blog/choosing-a-backend-when-you-manage-multiple-client-projects/cover.png is excluded by !**/*.png
• static/images/blog/how-modern-developers-choose-tech-stacks-today/cover.png is excluded by !**/*.png
• static/images/blog/how-open-source-developers-use-appwrite/cover.png is excluded by !**/*.png
• static/images/blog/self-serve-compliance-what-teams-expect-in-2026/cover.png is excluded by !**/*.png

📒 Files selected for processing (5)

• .optimize-cache.json
• src/routes/blog/post/choosing-a-backend-when-you-manage-multiple-client-projects/+page.markdoc
• src/routes/blog/post/how-modern-developers-choose-tech-stacks-today/+page.markdoc
• src/routes/blog/post/how-open-source-developers-use-appwrite/+page.markdoc
• src/routes/blog/post/self-serve-compliance-what-teams-expect-in-2026/+page.markdoc

[adityaoberai]

not necessary here

[adityaoberai]

unnecessary

[adityaoberai]

We need to talk about other products too, not just sites