Add 10 new SEO blogs

[adityaoberai]

What does this PR do?

(Provide a description of what this PR does.)

Test Plan

(Write your test plan here. If you changed any code, please provide us with clear instructions on how you verified your changes work.)

Related PRs and Issues

(If this PR is related to any other PR or resolves any issue or related to any issue link all related PR and issues here.)

Have you read the Contributing Guidelines on issues?

(Write your answer here.)

[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

Appwrite has crossed the 50K GitHub stars milestone with hundreds of active contributors

[greptile-apps]

Greptile Summary

This PR adds 10 new SEO-focused blog posts covering vibe coding topics — startup ideas, agency workflows, backend/frontend selection, security mistakes, production deployment, hidden platform costs, and the impact on junior developers. All posts include structured frontmatter with FAQs, author attribution, cover images, and internal cross-links.

• All 10 posts are currently marked unlisted: true; they will not appear in the blog listing or be indexed until that flag is removed (flagged in a previous review thread).
• Internal links to companion posts (/blog/post/backend-checklist-vibe-coded-apps, /blog/post/comparing-vibe-coding-tools, /blog/post/vibe-coding-security-best-practices) were verified to exist in the repository.
• One minor grammar error was found in best-frontend-frameworks-for-vibe-coding: "one of the strongest default" should be "one of the strongest defaults".

Confidence Score: 5/5

All 10 posts are content-only additions with no code or routing logic changes; safe to merge.

These are purely content additions — new markdoc blog posts and static cover images. Internal cross-links were verified to resolve to existing posts in the repository. The only finding is a single grammar nit in one post. No functional or structural issues were identified.

best-frontend-frameworks-for-vibe-coding/+page.markdoc has a one-word grammar fix ("default" to "defaults")

Important Files Changed

Filename	Overview
src/routes/blog/post/25-startup-ideas-you-can-build-with-vibe-coding/+page.markdoc	New blog post listing 25 vibe-coded startup ideas with Appwrite integration guidance; marked unlisted: true
src/routes/blog/post/agencies-vibe-coding-client-projects/+page.markdoc	New blog post on agency vibe coding workflows and client project delivery; no issues found
src/routes/blog/post/best-backend-for-vibe-coding-apps/+page.markdoc	New backend comparison post; previously noted duplicate paragraph in Appwrite section
src/routes/blog/post/best-frontend-frameworks-for-vibe-coding/+page.markdoc	New frontend frameworks comparison post; contains one grammar error
src/routes/blog/post/can-vibe-coding-replace-junior-developers/+page.markdoc	New post on the impact of vibe coding on junior developer roles; content and links look correct
src/routes/blog/post/deploy-vibe-coding-projects-to-production/+page.markdoc	New step-by-step production deployment guide; Teams link correctly uses /docs/products/auth/teams
src/routes/blog/post/hidden-costs-of-vibe-coding-platforms/+page.markdoc	New post covering token billing, lock-in, and schema risks of vibe coding platforms; no issues found
src/routes/blog/post/how-vibe-coding-is-changing-software-development/+page.markdoc	New overview post on how vibe coding shifts developer workflows; content and internal links are correct
src/routes/blog/post/vibe-coding-security-mistakes/+page.markdoc	New security-focused post covering 16 common vibe coding mistakes; all internal links resolve correctly
src/routes/blog/post/vibe-coding-vs-traditional-development/+page.markdoc	New comparative post on vibe coding vs traditional development; content is well-structured with no issues

_{Reviews (7): Last reviewed commit: "Merge branch 'main' into aditya/add-new-..." | Re-trigger Greptile}

[greptile-apps]

All 10 posts are marked unlisted: true

The PR title describes these as "SEO blogs", but unlisted: true prevents them from appearing in the blog listing and from being crawled and indexed. This pattern appears on all 10 new posts. If public visibility is intended at merge time, this flag should be removed or set to false across all 10 posts. If this is a staged rollout reviewed before going live, no action is needed here — but it is worth confirming the flag will be cleared before the SEO value is expected.