Skip to content

SEO blogs#2821

Merged
adityaoberai merged 14 commits intomainfrom
newblogs
Mar 19, 2026
Merged

SEO blogs#2821
adityaoberai merged 14 commits intomainfrom
newblogs

Conversation

@aishwaripahwa12
Copy link
Contributor

@aishwaripahwa12 aishwaripahwa12 commented Mar 19, 2026

3 new SEO blogs on how developer tools are evolving in 2026, a practical comparison between self-hosted and managed backends, and the fastest way to launch your next side project.

Summary by CodeRabbit

  • Documentation
    • Three new unlisted blog posts published: overview of developer tools in 2026, a practical comparison of self-hosted vs managed backends, and a guide to launching side projects/MVPs.
  • Chores
    • Added cache entries for the three posts' cover images to ensure thumbnails render correctly.

@coderabbitai
Copy link
Contributor

coderabbitai bot commented Mar 19, 2026

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 three new Markdoc blog posts under src/routes/blog/post/: how-developer-tools-are-evolving-in-2026, self-hosted-vs-managed-backends-a-practical-comparison, and the-fastest-way-to-launch-your-next-side-project. Each file includes frontmatter metadata (layout, title, description, date, cover image, read time, author, category, featured/unlisted flags) and full article content. The .optimize-cache.json file is updated with three new hashed entries for the corresponding cover images. No existing files or exported/public code entities were modified.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name Status Explanation Resolution
Title check ❓ Inconclusive The title 'SEO blogs' is overly vague and generic—it uses a non-descriptive term that doesn't convey meaningful information about the specific blog posts being added. Use a more descriptive title that specifies the main content, such as 'Add three blog posts about developer tools, backend architectures, and side projects' or 'Add blog posts on 2026 developer tools, self-hosted vs managed backends, and side project launch strategies'.
✅ 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 newblogs
📝 Coding Plan
  • Generate coding plan for human review comments

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

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

@greptile-apps
Copy link
Contributor

greptile-apps bot commented Mar 19, 2026

Greptile Summary

This PR adds three new SEO-focused blog posts along with their cover images: a piece on how developer tools are evolving in 2026, a practical comparison of self-hosted vs. managed backends, and a guide on launching side projects quickly. All posts follow the established frontmatter conventions (valid aishwari author, correct categories, unlisted: true), and the .optimize-cache.json file is updated correctly for the new cover images.

Two minor consistency issues were found:

  • The description field of the self-hosted vs. managed backends post uses "self hosted" (unhyphenated) while the title, URL, and body all use "self-hosted".
  • The side-project post uses "real-time" (hyphenated) throughout, while the other two new posts and Appwrite's existing content use "realtime" (one word) to match the product branding.

Confidence Score: 5/5

  • This PR is safe to merge; it only adds new content files and a cache update with no functional code changes.
  • All three blog posts are structurally sound, use valid frontmatter fields, reference a real author, and are marked unlisted: true. The only issues are minor style inconsistencies in phrasing ("self hosted" and "real-time" vs. "realtime") that have no functional impact.
  • No files require special attention beyond the two style notes in self-hosted-vs-managed-backends-a-practical-comparison/+page.markdoc and the-fastest-way-to-launch-your-next-side-project/+page.markdoc.

Important Files Changed

Filename Overview
src/routes/blog/post/how-developer-tools-are-evolving-in-2026/+page.markdoc New SEO blog post about developer tool trends in 2026. Frontmatter is well-formed with a valid author, correct category, and unlisted: true. Content is consistent and uses "realtime" (one word) throughout, matching Appwrite's product naming.
src/routes/blog/post/self-hosted-vs-managed-backends-a-practical-comparison/+page.markdoc New SEO blog comparing self-hosted vs. managed backends. The description frontmatter field uses "self hosted" (unhyphenated) while the title, URL slug, and rest of the article use "self-hosted", creating a minor inconsistency. Content and structure are otherwise sound.
src/routes/blog/post/the-fastest-way-to-launch-your-next-side-project/+page.markdoc New SEO blog on launching side projects quickly. Uses "real-time" (hyphenated) throughout, while the other two new posts and Appwrite's own product naming use "realtime" (one word), creating cross-post inconsistency.
.optimize-cache.json Cache file updated with SHA hashes for the three new cover images. Changes look correct and consistent with existing entries.

Last reviewed commit: "three new SEO blogs"

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

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/self-hosted-vs-managed-backends-a-practical-comparison/`+page.markdoc:
- Line 4: Update the frontmatter description string: replace the phrase "self
hosted" with hyphenated "self-hosted" to match the title and standard usage;
locate the description field in the page frontmatter (the line starting with
description:) in the self-hosted vs managed backends page and change only that
token so the sentence reads "...Compare self-hosted and managed backends..."
preserving the rest of the text.

In
`@src/routes/blog/post/the-fastest-way-to-launch-your-next-side-project/`+page.markdoc:
- Line 100: The sentence beginning "Appwrite exists so you don't have to make
that trade-off." is hard to read due to stacked appositives; rewrite it to list
features cleanly and then state the benefit. Replace that sentence with a
tightened version such as: "Appwrite provides production-ready authentication,
databases, storage, functions, and real-time features in a single platform—set
up your backend in minutes and spend your time building what only you can."
Update the line in +page.markdoc accordingly.

ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: b7c75ed5-ef40-4b6a-b3bb-417dde23d739

📥 Commits

Reviewing files that changed from the base of the PR and between 03a0dd1 and 5bdd110.

⛔ Files ignored due to path filters (3)
  • static/images/blog/how-developer-tools-are-evolving-in-2026/cover.png is excluded by !**/*.png
  • static/images/blog/self-hosted-vs-managed-backends-a-practical-comparison/cover.png is excluded by !**/*.png
  • static/images/blog/the-fastest-way-to-launch-your-next-side-project/cover.png is excluded by !**/*.png
📒 Files selected for processing (4)
  • .optimize-cache.json
  • src/routes/blog/post/how-developer-tools-are-evolving-in-2026/+page.markdoc
  • src/routes/blog/post/self-hosted-vs-managed-backends-a-practical-comparison/+page.markdoc
  • src/routes/blog/post/the-fastest-way-to-launch-your-next-side-project/+page.markdoc

aishwaripahwa12 and others added 2 commits March 19, 2026 15:34
…al-comparison/+page.markdoc

Co-authored-by: greptile-apps[bot] <165735046+greptile-apps[bot]@users.noreply.github.com>
…project/+page.markdoc

Co-authored-by: greptile-apps[bot] <165735046+greptile-apps[bot]@users.noreply.github.com>
Comment on lines +105 to +111
**One permission model across everything.** Auth rules, database access, storage permissions, and function triggers all share the same system. No synchronization logic, no mismatched SDKs, no gaps where things quietly break.

**Realtime as a first-class primitive.** Structured, server-side filtered subscriptions are built in, not a third-party integration bolted on after the fact. Live dashboards and collaborative features work the way developers now expect them to.

**Type safety without the maintenance.** Auto-generated SDKs stay in sync with your backend schema automatically. What's defined in the backend is what the client sees, no drift, no surprises as the product evolves.

**Ship anywhere, without trade-offs.** Appwrite is fully open-source and container-native. Run it locally during development, self-host it for compliance or data residency, or use Appwrite Cloud when you'd rather skip the infrastructure entirely. The platform follows your team's needs, not the other way around.
Copy link
Member

Choose a reason for hiding this comment

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

These should have bullets


One of the most common mistakes developers make is treating a side project like a full-scale production system before a single user has signed up, worrying about scaling to millions of users, perfect backend architecture, and a complete feature set before anything exists.

This is the problem Appwrite is built to solve. Appwrite is an open-source developer platform that gives you the backend pieces most side projects need out of the box: authentication, databases, storage, functions, realtime, and messaging. Everything works together without extra integration work. Instead of spending days on infrastructure, you can have a working backend in minutes and move straight to the part that makes your side project worth building.
Copy link
Member

Choose a reason for hiding this comment

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

Needs to mention web hosting too

Copy link
Member

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

Final few changes

aishwaripahwa12 and others added 5 commits March 20, 2026 00:25
Co-authored-by: Aditya Oberai <adityaoberai1@gmail.com>
Co-authored-by: Aditya Oberai <adityaoberai1@gmail.com>
Co-authored-by: Aditya Oberai <adityaoberai1@gmail.com>
Co-authored-by: Aditya Oberai <adityaoberai1@gmail.com>
@adityaoberai adityaoberai merged commit 1cb693b into main Mar 19, 2026
6 checks passed
@adityaoberai adityaoberai deleted the newblogs branch March 19, 2026 22:02
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