Skip to content

New SEO blogs#2838

Open
aishwaripahwa12 wants to merge 1 commit intomainfrom
aishwari/seoblogs1
Open

New SEO blogs#2838
aishwaripahwa12 wants to merge 1 commit intomainfrom
aishwari/seoblogs1

Conversation

@aishwaripahwa12
Copy link
Copy Markdown
Contributor

@aishwaripahwa12 aishwaripahwa12 commented Mar 30, 2026

Added three new blogs

Summary by CodeRabbit

  • New Features
    • Added three new blog posts exploring SDK design practices, evaluating backend platform features, and the impact of quality documentation on developer experience.

@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai bot commented Mar 30, 2026

Walkthrough

This pull request adds three new blog post pages to a documentation site and updates the image cache configuration. The changes include three new Markdoc blog post files—covering SDK design, backend platform criteria, and documentation value—each containing frontmatter metadata (title, description, publication date, cover image, author, category, and visibility flags) and article content. Additionally, the cache configuration file is updated with three new entries mapping blog cover image paths to hash values. No existing entries are modified or removed.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~12 minutes

🚥 Pre-merge checks | ✅ 3
✅ Passed checks (3 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title 'New SEO blogs' accurately reflects the main change—three new blog posts were added to the website.
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 aishwari/seoblogs1

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.

Copy link
Copy Markdown
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: 1

🤖 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/why-documentation-is-the-most-underrated-developer-feature/`+page.markdoc:
- Line 50: Update the two copy issues in the Markdoc page: change
"StackOverflow" to "Stack Overflow" in the sentence starting with "Poor
documentation search is a silent killer..." (the line referencing Google and
StackOverflow), and adjust the verb for the phrase containing "platforms and
documentation quality" to use plural agreement by replacing the current verb
with "matter" so it reads "...platforms and documentation quality matter."
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: e7bc4217-577d-464e-9959-240f46b0440f

📥 Commits

Reviewing files that changed from the base of the PR and between 0d0ed18 and 00e9156.

⛔ Files ignored due to path filters (3)
  • static/images/blog/the-underrated-value-of-great-sdk-design/cover.png is excluded by !**/*.png
  • static/images/blog/what-developers-actually-want-from-a-backend-platform/cover.png is excluded by !**/*.png
  • static/images/blog/why-documentation-is-the-most-underrated-developer-feature/cover.png is excluded by !**/*.png
📒 Files selected for processing (4)
  • .optimize-cache.json
  • src/routes/blog/post/the-underrated-value-of-great-sdk-design/+page.markdoc
  • src/routes/blog/post/what-developers-actually-want-from-a-backend-platform/+page.markdoc
  • src/routes/blog/post/why-documentation-is-the-most-underrated-developer-feature/+page.markdoc


## Search that actually works

Poor documentation search is a silent killer. If a developer cannot find the right page in two or three queries, they will reach for Google instead, and Google may send them to outdated StackOverflow threads rather than your canonical docs.
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.

⚠️ Potential issue | 🟡 Minor

Fix two minor copy issues in reader-facing text.

Line 50 should use “Stack Overflow”, and Line 85 should use plural agreement (“matter”) with “platforms and documentation quality.”

✍️ Proposed copy fix
- Poor documentation search is a silent killer. If a developer cannot find the right page in two or three queries, they will reach for Google instead, and Google may send them to outdated StackOverflow threads rather than your canonical docs.
+ Poor documentation search is a silent killer. If a developer cannot find the right page in two or three queries, they will reach for Google instead, and Google may send them to outdated Stack Overflow threads rather than your canonical docs.

- If you are evaluating backend platforms and documentation quality matters to you, the following links are a good starting point.
+ If you are evaluating backend platforms and documentation quality matter to you, the following links are a good starting point.

Also applies to: 85-85

🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In
`@src/routes/blog/post/why-documentation-is-the-most-underrated-developer-feature/`+page.markdoc
at line 50, Update the two copy issues in the Markdoc page: change
"StackOverflow" to "Stack Overflow" in the sentence starting with "Poor
documentation search is a silent killer..." (the line referencing Google and
StackOverflow), and adjust the verb for the phrase containing "platforms and
documentation quality" to use plural agreement by replacing the current verb
with "matter" so it reads "...platforms and documentation quality matter."

@greptile-apps
Copy link
Copy Markdown
Contributor

greptile-apps bot commented Mar 30, 2026

Greptile Summary

This PR adds three new SEO-focused blog posts authored by aishwari (Aishwari Pahwa), each paired with a cover image and a corresponding .optimize-cache.json entry. The posts are well-written, internally consistent, and use valid internal links throughout (including the referenced /blog/post/baas-vs-custom-backend).

Key observations:

  • All three posts are marked unlisted: true, which means they will not appear in the main blog feed after merging — they are only reachable via direct URL. This may be intentional staging, but should be confirmed before merge if the goal is public visibility.
  • Publish dates are set to 2026-03-31 (tomorrow), which is consistent with a next-day coordinated launch.
  • The author: aishwari slug resolves correctly to the existing author profile.
  • Cover images are present for all three posts and their hashes are correctly registered in .optimize-cache.json.

Confidence Score: 5/5

Safe to merge — all three posts are structurally correct with valid links, images, and author references; the only open question is whether unlisted: true is intentional.

All remaining findings are P2 (style/intent clarification). The unlisted: true flag is a valid frontmatter option used by other posts in the repo, so it won't cause any runtime errors — it simply controls blog feed visibility, which may be intentional for staged rollout.

The three +page.markdoc files should have unlisted: true removed if the posts are intended to appear in the public blog feed immediately after merge.

Important Files Changed

Filename Overview
src/routes/blog/post/the-underrated-value-of-great-sdk-design/+page.markdoc New blog post on SDK design; well-structured content with valid internal links and correct author slug, but marked unlisted: true which hides it from the main blog feed.
src/routes/blog/post/what-developers-actually-want-from-a-backend-platform/+page.markdoc New blog post on backend platform evaluation; internal link to /blog/post/baas-vs-custom-backend is valid, but also marked unlisted: true.
src/routes/blog/post/why-documentation-is-the-most-underrated-developer-feature/+page.markdoc New blog post on documentation quality; well-written with appropriate internal doc links, but also marked unlisted: true.
.optimize-cache.json Adds image hashes for all three new blog cover images; entries are correctly placed in alphabetical order.

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

author: aishwari
category: product
featured: false
unlisted: true
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.

P2 unlisted: true on all three new posts

All three new blog posts (the-underrated-value-of-great-sdk-design, what-developers-actually-want-from-a-backend-platform, and why-documentation-is-the-most-underrated-developer-feature) are marked unlisted: true. This flag prevents them from appearing in the main blog feed, making them only accessible via direct URL after merge.

If the intent is to stage them for review before a coordinated public launch, this is fine. But if these are meant to go live immediately upon merge (as the PR title "New SEO blogs" suggests), all three posts should have unlisted removed or set to false.

Suggested change
unlisted: true
---
layout: post
title: The underrated value of great SDK design
description: "Great SDK design can make or break developer adoption. Here's why SDK quality matters, and what developers actually expect from modern backend platforms."
date: 2026-03-31
cover: /images/blog/the-underrated-value-of-great-sdk-design/cover.png
timeToRead: 5
author: aishwari
category: product
featured: false
---

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