feat: blog post cold start improvements

[levivannoort]

What does this PR do?

Adds a new blog to the website.

Test Plan

N/A

Related PRs and Issues

N/A

Have you read the Contributing Guidelines on issues?

Yes

Summary by CodeRabbit

• Documentation
  • Added new author profile for Levi van Noort.
  • Added blog post documenting cold-start performance improvements for Appwrite Sites, including optimization techniques and quantified results showing 30–50% reduction in cold-start duration.

[coderabbitai]

Walkthrough

The pull request adds two new Markdoc files to the blog section. The first introduces a new author profile for Levi van Noort with basic metadata. The second adds a detailed blog post documenting performance optimizations for Appwrite Sites, covering observability improvements, compression techniques using igzip, Node file tracing implementations, and quantified results showing 30–50% cold-start reductions. Both files are new content additions with no modifications to existing files.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~12 minutes

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title check	✅ Passed	The PR title 'feat: blog post cold start improvements' directly and specifically describes the main changes, which add a new blog post about cold start performance improvements for Appwrite Sites.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.

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

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch CLO-4110

📝 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

• X
• Mastodon
• Reddit
• LinkedIn

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

[coderabbitai]

🧹 Nitpick comments (1)

src/routes/blog/post/reducing-cold-starts-appwrite-sites/+page.markdoc (1)

48-48: Minor: Inconsistent dash formatting.

The sentence has inconsistent spacing around dashes: "download phase - previously" (space-dash-space) vs "steps-dropped" (no spaces). Consider using em-dashes consistently:

✏️ Suggested fix

-Those smaller artifacts translated directly into faster cold starts. With build outputs reduced by up to 99%, the download phase - previously one of the more costly steps-dropped from multiple seconds to just 100–200 milliseconds. Extraction saw a similar improvement, going from regular 4–7 second spikes down to around 200–400 milliseconds. Together, these two phases went from dominating the cold-start timeline to being barely noticeable.
+Those smaller artifacts translated directly into faster cold starts. With build outputs reduced by up to 99%, the download phase—previously one of the more costly steps—dropped from multiple seconds to just 100–200 milliseconds. Extraction saw a similar improvement, going from regular 4–7 second spikes down to around 200–400 milliseconds. Together, these two phases went from dominating the cold-start timeline to being barely noticeable.

🤖 Prompt for AI Agents

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

In `@src/routes/blog/post/reducing-cold-starts-appwrite-sites/`+page.markdoc at
line 48, The sentence has inconsistent dash spacing ("download phase -
previously" vs "steps-dropped"); update the punctuation in the Markdoc content
so both occurrences use a consistent em-dash style (e.g., change "download phase
- previously" to "download phase—previously" and "steps-dropped" to
"steps—dropped") ensuring the same em-dash usage across the paragraph.

🤖 Prompt for all review comments with AI agents

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

Nitpick comments:
In `@src/routes/blog/post/reducing-cold-starts-appwrite-sites/`+page.markdoc:
- Line 48: The sentence has inconsistent dash spacing ("download phase -
previously" vs "steps-dropped"); update the punctuation in the Markdoc content
so both occurrences use a consistent em-dash style (e.g., change "download phase
- previously" to "download phase—previously" and "steps-dropped" to
"steps—dropped") ensuring the same em-dash usage across the paragraph.

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: bfeea003-300d-4c67-9e3b-dba3340513a1

📥 Commits

Reviewing files that changed from the base of the PR and between 0154be8 and dc75779.

⛔ Files ignored due to path filters (3)

• bun.lock is excluded by !**/*.lock
• static/images/avatars/levi.png is excluded by !**/*.png
• static/images/blog/reducing-cold-starts-appwrite-sites/cover.png is excluded by !**/*.png

📒 Files selected for processing (2)

• src/routes/blog/author/levi-van-noort/+page.markdoc
• src/routes/blog/post/reducing-cold-starts-appwrite-sites/+page.markdoc

[greptile-apps]

Greptile Summary

This PR adds a new blog post titled "How we reduced cold start times on Appwrite Sites" along with a new author profile for Levi van Noort. The post covers three main optimizations: adding observability, switching from gzip to igzip for decompression (yielding 50–100% faster extraction), and implementing Node file tracing to dramatically reduce build artifact sizes (up to 99% reduction), with an overall 30–50% cold-start time improvement.

Key changes:

• New blog post at src/routes/blog/post/reducing-cold-starts-appwrite-sites/+page.markdoc with performance data and a comparison table
• New author page at src/routes/blog/author/levi-van-noort/+page.markdoc
• New static assets: author avatar and blog cover image
• Minor bun.lock integrity hash update for @appwrite.io/specs

Issues found:

• A missing closing dash and space on line 48 (steps-dropped → steps - dropped) makes the parenthetical clause grammatically incorrect
• Only the first section heading carries an anchor ID ({% #adding-observability %}); the remaining five headings are missing theirs, breaking deep-link consistency

Confidence Score: 4/5

• Safe to merge after fixing the minor punctuation error and adding missing heading anchor IDs.
• The PR is content-only (a blog post + author page) with no functional code changes. The only issues are a punctuation typo on line 48 and inconsistent anchor IDs on section headings — both are low-risk editorial issues that don't affect site functionality but would appear in the published article.
• src/routes/blog/post/reducing-cold-starts-appwrite-sites/+page.markdoc — review the punctuation fix on line 48 and add missing anchor IDs to section headings.

Important Files Changed

Filename	Overview
src/routes/blog/post/reducing-cold-starts-appwrite-sites/+page.markdoc	New blog post on cold-start improvements; well-structured with good data, but has a missing space/dash in a sentence on line 48 and inconsistent use of heading anchor IDs across sections.
src/routes/blog/author/levi-van-noort/+page.markdoc	New author profile page following the existing convention; no issues found.
bun.lock	Lockfile update adding an integrity hash for @appwrite.io/specs; expected artifact of running bun install, no issues.

_{Last reviewed commit: "Merge branch 'main' ..."}

[greptile-apps]

Missing space creates run-on clause

The phrase steps-dropped is missing a space and a closing dash before dropped. The parenthetical aside - previously one of the more costly steps - requires a matching closing dash to wrap the clause correctly.

Suggested change

Those smaller artifacts translated directly into faster cold starts. With build outputs reduced by up to 99%, the download phase - previously one of the more costly steps-dropped from multiple seconds to just 100–200 milliseconds. Extraction saw a similar improvement, going from regular 4–7 second spikes down to around 200–400 milliseconds. Together, these two phases went from dominating the cold-start timeline to being barely noticeable.

Those smaller artifacts translated directly into faster cold starts. With build outputs reduced by up to 99%, the download phase - previously one of the more costly steps - dropped from multiple seconds to just 100–200 milliseconds. Extraction saw a similar improvement, going from regular 4–7 second spikes down to around 200–400 milliseconds. Together, these two phases went from dominating the cold-start timeline to being barely noticeable.

[greptile-apps]

Inconsistent section anchor IDs

Only the first heading (# Adding observability) has an anchor ID ({% #adding-observability %}), but the remaining five headings do not. This is inconsistent and prevents deep-linking to individual sections for the other parts of the article.

Consider adding anchor IDs to the remaining headings for consistency:

# Compression and decompression {% #compression-and-decompression %}
# Node file tracing {% #node-file-tracing %}
# Cold starts {% #cold-starts %}
# Benefit from this change {% #benefit-from-this-change %}
# What's next {% #whats-next %}