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	Queued	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 about vibe coding, each paired with a cover image. The posts cover topics including startup ideas, agency workflows, backend/frontend selection, security, deployment, and comparisons with traditional development.

• All 10 posts are new .markdoc files with frontmatter, FAQs, and inline Appwrite product/tooling links; all internal cross-references resolve to existing blog routes.
• All posts are currently marked unlisted: true (addressed in a prior thread) and one post contains a minor grammar error (\"strongest default\" → \"strongest defaults\").

Confidence Score: 5/5

Safe to merge — purely additive content changes with no logic or infrastructure risk.

All 10 new blog posts are additive content files with no code changes. Internal links were verified against the repo and all resolve correctly. The only finding is a minor grammar nit in one post.

No files require special attention.

Important Files Changed

Filename	Overview
src/routes/blog/post/25-startup-ideas-you-can-build-with-vibe-coding/+page.markdoc	New 181-line blog post listing 25 vibe-coding startup ideas with Appwrite primitives. All internal links resolve; marked unlisted: true.
src/routes/blog/post/agencies-vibe-coding-client-projects/+page.markdoc	New 123-line post on agency workflows with vibe coding. Internal cross-links all resolve; marked unlisted: true.
src/routes/blog/post/best-backend-for-vibe-coding-apps/+page.markdoc	New 123-line backend comparison post (Appwrite vs Supabase vs Firebase vs Convex vs Neon). Internal links resolve; marked unlisted: true.
src/routes/blog/post/best-frontend-frameworks-for-vibe-coding/+page.markdoc	New 127-line frontend framework guide. Contains one grammar error ("strongest default" → "strongest defaults"); marked unlisted: true.
src/routes/blog/post/can-vibe-coding-replace-junior-developers/+page.markdoc	New 89-line post on junior developers and vibe coding. Content and links look correct; marked unlisted: true.
src/routes/blog/post/deploy-vibe-coding-projects-to-production/+page.markdoc	New 149-line step-by-step deployment guide. Teams link and all internal links resolve correctly; marked unlisted: true.
src/routes/blog/post/hidden-costs-of-vibe-coding-platforms/+page.markdoc	New 101-line post covering token costs, lock-in, and schema risks. All cross-links resolve; marked unlisted: true.
src/routes/blog/post/how-vibe-coding-is-changing-software-development/+page.markdoc	New 87-line overview of how vibe coding shifts development workflows. All links resolve; marked unlisted: true.
src/routes/blog/post/vibe-coding-security-mistakes/+page.markdoc	New 146-line post covering 16 security mistakes in vibe-coded apps. Content is thorough; all linked posts resolve; marked unlisted: true.
src/routes/blog/post/vibe-coding-vs-traditional-development/+page.markdoc	New 107-line comparison post. All cross-references resolve; marked unlisted: true.

_{Reviews (5): Last reviewed commit: "Update src/routes/blog/post/25-startup-i..." | 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.