SEO Blogs

[aishwaripahwa12]

Latest SEO blogs, with the cloud computing SEO blog and its associated image removed, followed by re-running image optimization to refresh the optimize cache.

[appwrite]

Appwrite Website

Project ID: 69d7efb00023389e8d27

Sites (1)

Site	Status	Logs	Preview	QR
website 69d7f2670014e24571ca	Failed	View Logs	Preview URL

Website (appwrite/website)

Project ID: 684969cb000a2f6c0a02

Sites (1)

Site	Status	Logs	Preview	QR
website 68496a17000f03d62013	Queued	View Logs	Preview URL

---

Tip

Function scopes give you fine-grained control over API permissions

[greptile-apps]

Greptile Summary

This PR adds three new SEO-focused blog posts (cloud storage, Kubernetes, and serverless) along with their cover images, and refreshes the image optimization cache after removing a previous cloud computing post. All three posts are marked unlisted: true, keeping them out of public listings while they are indexed by search engines.

• Three new markdoc blog posts added with correct frontmatter (valid authors, matching cover image paths, proper category and FAQ fields), each paired with a committed .avif cover image.
• .optimize-cache.json updated with cache entries for all three new image directories; the .png-vs-.avif extension difference in the cache is intentional per project convention.

Confidence Score: 5/5

Safe to merge — content-only additions with no functional code changes.

Three new blog posts and their cover images are self-contained additions. Frontmatter fields (authors, cover paths, categories) are all valid and consistent with existing posts, every new image directory has a corresponding cache entry, and the posts are gated behind unlisted: true. No logic, configuration, or infrastructure is affected.

No files require special attention.

Important Files Changed

Filename	Overview
src/routes/blog/post/what-is-cloud-storage-an-expert-guide-for-developers/+page.markdoc	New SEO blog post on cloud storage; frontmatter, cover path, author, and FAQ all look correct. Marked unlisted.
src/routes/blog/post/what-is-kubernetes-an-expert-guide-for-developers/+page.markdoc	New SEO blog post on Kubernetes; frontmatter, cover path, author (luke-silver), and internal links all correct. Marked unlisted.
src/routes/blog/post/what-is-serverless-an-expert-guide-for-developers/+page.markdoc	New SEO blog post on serverless computing; frontmatter, cover path, author (atharva), and content structure all correct. Marked unlisted.
.optimize-cache.json	Cache entries added for all three new blog cover images; extension mismatch (.png in cache vs .avif on disk) is intentional per project convention. All three new image directories have corresponding cache entries.

_{Reviews (3): Last reviewed commit: "Apply suggestion from @aishwaripahwa12" | Re-trigger Greptile}

[greptile-apps]

Broken internal link points to blog homepage instead of the serverless guide. The link text reads "our guide to serverless" but the URL is https://appwrite.io/blog, which takes readers to the blog index rather than the specific article. It should be https://appwrite.io/blog/post/what-is-serverless-an-expert-guide-for-developers, the companion post added in this same PR.

[atharvadeosthale]

@copilot I wanted to go ahead and remove the cloud computing article. Along with that, I also want to remove the image associated with it. And then what I wanted to do is run bun run optimize. This will optimize the images again, and it will update the image cache JSON. Then go over and check again if everything is fine, and if everything is fine, just go ahead and push to this PR.

[Copilot]

@copilot I wanted to go ahead and remove the cloud computing article. Along with that, I also want to remove the image associated with it. And then what I wanted to do is run `bun run op...

Implemented in commit 4b3d0bd.

• Removed the cloud computing blog post
• Removed its associated image
• Ran bun run optimize
• Removed the stale cloud-computing entry from .optimize-cache.json

I also rechecked the repo for references to that blog slug and found none.

[adityaoberai]

Let's add Luke or Levi as the author please