screenshot automation blog by aishwaripahwa12 · Pull Request #2792 · appwrite/website

aishwaripahwa12 · 2026-03-10T08:03:38Z

a new blog post about solving the headaches of screenshot automation (and why an API-First approach works better)

Summary by CodeRabbit

Documentation
- Published new blog post covering screenshot automation challenges, comparison of implementation approaches, and practical guidance for API-first screenshot generation.

coderabbitai · 2026-03-10T08:04:19Z

Warning

Rate limit exceeded

@adityaoberai has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 4 minutes and 46 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 42655d1e-2339-4899-9aeb-85084ddadd6f

📥 Commits

Reviewing files that changed from the base of the PR and between de12051 and c9ec195.

📒 Files selected for processing (1)

src/routes/blog/post/solving-the-headaches-of-screenshot-automation-and-why-an-api-first-approach-works-better/+page.markdoc

Walkthrough

This pull request adds a new blog post about screenshot automation and API-first approaches. The blog post is added to a new route and includes discussion of screenshot automation challenges, comparison of different approaches, and details about an API-based solution with code examples. An entry is also added to the optimization cache file with the hash of the blog post's cover image.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 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 clearly and accurately summarizes the main change: adding a new blog post about screenshot automation.
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
Post copyable unit tests in a comment
Commit unit tests in branch screenshotautomation

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

coderabbitai

Actionable comments posted: 3

🤖 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/solving-the-headaches-of-screenshot-automation-and-why-an-api-first-approach-works-better/`+page.markdoc:
- Line 80: The second-level heading hierarchy is broken because the heading
"Hosted screenshot APIs (Pricing, pros, and cons)" is using a top-level marker;
change the current "# 2. Hosted screenshot APIs (Pricing, pros, and cons)" to a
second-level heading "## 2. Hosted screenshot APIs (Pricing, pros, and cons)" so
it follows the preceding "## 1." section and restores correct TOC/outline
generation.
- Line 5: The frontmatter "date" field for this post is set to 2026-03-11 which
will make the article appear immediately with a future timestamp because the
blog listing does not filter future-dated posts; either confirm the post is
intentionally scheduled for tomorrow or update the frontmatter key "date" to
2026-03-10 (edit the "date" value in the file's frontmatter) before merging.
- Around line 188-189: The prose incorrectly references a non-existent
screenshot() method and ScreenshotConfig object; update the text to state that
the SDK exposes avatars.getScreenshot({...}) and that options are passed
directly as parameters in the config object (as in the code sample), removing
references to screenshot() and ScreenshotConfig and ensuring the description
matches avatars.getScreenshot({...}) usage.

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: eb4fbb35-95ff-4066-b70b-1efd9e580b0d

📥 Commits

Reviewing files that changed from the base of the PR and between d8c505f and de12051.

⛔ Files ignored due to path filters (1)

static/images/blog/solving-the-headaches-of-screenshot-automation-and-why-an-api-first-approach-works-better/cover.png is excluded by !**/*.png

📒 Files selected for processing (2)

.optimize-cache.json
src/routes/blog/post/solving-the-headaches-of-screenshot-automation-and-why-an-api-first-approach-works-better/+page.markdoc

coderabbitai · 2026-03-10T08:12:30Z

...-headaches-of-screenshot-automation-and-why-an-api-first-approach-works-better/+page.markdoc

+layout: post
+title: Solving the headaches of screenshot automation (and why an API-First approach works better)
+description: Generating screenshots at scale is harder than it looks. This guide breaks down the challenges of screenshot automation and why an API-first approach works better.
+date: 2026-03-11


⚠️ Potential issue | 🟡 Minor

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash # Verify whether blog pages hide future-dated posts. # Expected: if scheduled publishing is supported, there should be a comparison against the current date. rg -n -C2 'new Date|Date\.parse|post\.date|frontmatter\.date|sort\(' src/routes/blog src/lib

Repository: appwrite/website

Length of output: 16774

🏁 Script executed:

# Search for how isNewUntil is used and if there's filtering logic for blog posts rg -n 'isNewUntil|filter.*date|date.*filter' src/routes/blog # Also search for the blog page server logic fd -n '\+page.server.ts' src/routes/blog

Repository: appwrite/website

Length of output: 1734

🏁 Script executed:

# Find page.server.ts files in blog routes find src/routes/blog -name '+page.server.ts' -o -name '+page.svelte' # Search for isNewUntil usage rg 'isNewUntil'

Repository: appwrite/website

Length of output: 3025

🏁 Script executed:

# Read the content.ts file to see the full post loading/sorting logic cat src/routes/blog/content.ts

Repository: appwrite/website

Length of output: 3447

Confirm the publish date before merging.

The post date is set to 2026-03-11, which is tomorrow relative to March 10, 2026. The blog listing does not filter future-dated posts—posts are sorted by date and displayed immediately regardless of whether the date is in the future. This will cause the article to appear with a future publication timestamp on the blog. Please move the date to 2026-03-10 or confirm this post is intentionally scheduled for tomorrow.

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed. In `@src/routes/blog/post/solving-the-headaches-of-screenshot-automation-and-why-an-api-first-approach-works-better/`+page.markdoc at line 5, The frontmatter "date" field for this post is set to 2026-03-11 which will make the article appear immediately with a future timestamp because the blog listing does not filter future-dated posts; either confirm the post is intentionally scheduled for tomorrow or update the frontmatter key "date" to 2026-03-10 (edit the "date" value in the file's frontmatter) before merging.

...-headaches-of-screenshot-automation-and-why-an-api-first-approach-works-better/+page.markdoc

…ation-and-why-an-api-first-approach-works-better/+page.markdoc Co-authored-by: Aditya Oberai <adityaoberai1@gmail.com>

…ation-and-why-an-api-first-approach-works-better/+page.markdoc

a new blog post

de12051

coderabbitai bot reviewed Mar 10, 2026

View reviewed changes

Merge branch 'main' into screenshotautomation

5e9f565

adityaoberai requested changes Mar 10, 2026

View reviewed changes

aishwaripahwa12 and others added 14 commits March 11, 2026 13:58

Update src/routes/blog/post/solving-the-headaches-of-screenshot-autom…

46a089b

…ation-and-why-an-api-first-approach-works-better/+page.markdoc Co-authored-by: Aditya Oberai <adityaoberai1@gmail.com>

Update src/routes/blog/post/solving-the-headaches-of-screenshot-autom…

a3950aa

…ation-and-why-an-api-first-approach-works-better/+page.markdoc Co-authored-by: Aditya Oberai <adityaoberai1@gmail.com>

Update src/routes/blog/post/solving-the-headaches-of-screenshot-autom…

b898112

…ation-and-why-an-api-first-approach-works-better/+page.markdoc Co-authored-by: Aditya Oberai <adityaoberai1@gmail.com>

Update src/routes/blog/post/solving-the-headaches-of-screenshot-autom…

56fb6b8

…ation-and-why-an-api-first-approach-works-better/+page.markdoc Co-authored-by: Aditya Oberai <adityaoberai1@gmail.com>

Update src/routes/blog/post/solving-the-headaches-of-screenshot-autom…

0e8d038

…ation-and-why-an-api-first-approach-works-better/+page.markdoc Co-authored-by: Aditya Oberai <adityaoberai1@gmail.com>

Update src/routes/blog/post/solving-the-headaches-of-screenshot-autom…

70571ea

…ation-and-why-an-api-first-approach-works-better/+page.markdoc Co-authored-by: Aditya Oberai <adityaoberai1@gmail.com>

Update src/routes/blog/post/solving-the-headaches-of-screenshot-autom…

a0cdf2d

…ation-and-why-an-api-first-approach-works-better/+page.markdoc Co-authored-by: Aditya Oberai <adityaoberai1@gmail.com>

Update src/routes/blog/post/solving-the-headaches-of-screenshot-autom…

825c709

…ation-and-why-an-api-first-approach-works-better/+page.markdoc Co-authored-by: Aditya Oberai <adityaoberai1@gmail.com>

Update src/routes/blog/post/solving-the-headaches-of-screenshot-autom…

e50ed3b

…ation-and-why-an-api-first-approach-works-better/+page.markdoc Co-authored-by: Aditya Oberai <adityaoberai1@gmail.com>

Update src/routes/blog/post/solving-the-headaches-of-screenshot-autom…

bff2c63

…ation-and-why-an-api-first-approach-works-better/+page.markdoc Co-authored-by: Aditya Oberai <adityaoberai1@gmail.com>

Update src/routes/blog/post/solving-the-headaches-of-screenshot-autom…

391b126

…ation-and-why-an-api-first-approach-works-better/+page.markdoc

Update src/routes/blog/post/solving-the-headaches-of-screenshot-autom…

fe77f00

…ation-and-why-an-api-first-approach-works-better/+page.markdoc

Update src/routes/blog/post/solving-the-headaches-of-screenshot-autom…

e16353b

…ation-and-why-an-api-first-approach-works-better/+page.markdoc

Refine content and formatting in the screenshot automation blog post

c9ec195

adityaoberai approved these changes Mar 11, 2026

View reviewed changes

adityaoberai merged commit acc4753 into main Mar 11, 2026
6 checks passed

adityaoberai deleted the screenshotautomation branch March 11, 2026 18:49

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

screenshot automation blog#2792

screenshot automation blog#2792
adityaoberai merged 16 commits intomainfrom
screenshotautomation

aishwaripahwa12 commented Mar 10, 2026 •

edited by coderabbitai bot

Loading

Uh oh!

coderabbitai bot commented Mar 10, 2026 •

edited

Loading

Rate limit exceeded

Uh oh!

coderabbitai bot left a comment

Uh oh!

coderabbitai bot Mar 10, 2026

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

Conversation

aishwaripahwa12 commented Mar 10, 2026 • edited by coderabbitai bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Summary by CodeRabbit

Uh oh!

coderabbitai bot commented Mar 10, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Rate limit exceeded

Walkthrough

Estimated code review effort

Uh oh!

coderabbitai bot left a comment

Choose a reason for hiding this comment

Uh oh!

coderabbitai bot Mar 10, 2026

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

aishwaripahwa12 commented Mar 10, 2026 •

edited by coderabbitai bot

Loading

coderabbitai bot commented Mar 10, 2026 •

edited

Loading