Update Appwrite definition to be consistent across blogs #2367
Conversation
appwrite.ioProject ID: Note Appwrite has a Discord community with over 16 000 members. |
WalkthroughThis PR updates marketing copy across multiple blog posts to describe Appwrite as an “open-source, all-in-one cloud development platform” with built-in backend infrastructure and web hosting. It replaces prior BaaS/core-APIs descriptions, adds mentions of Authentication, Databases, Functions, Storage, Messaging, and framework/language flexibility, and occasionally adjusts link placement and formatting. Some posts add short “get-started” lists or expand existing ones. No code, logic, or exported/public entities are changed; all modifications are content-only within Markdoc pages. Possibly related PRs
Suggested reviewers
✨ Finishing Touches🧪 Generate unit tests
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. 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed help? Create a ticket on our support page for assistance with any issues or questions. CodeRabbit Commands (Invoked using PR/Issue comments)Type Other keywords and placeholders
CodeRabbit Configuration File (
|
adityaoberai
force-pushed
the
update-appwrite-definition
branch
from
9db5ae4 to
9c14cb0
Compare
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 0
🧹 Nitpick comments (2)
src/routes/blog/post/best-ios-android-app-development-platforms/+page.markdoc (2)
230-231: Tiny wording polish for cadence (optional)“all from a single place” → “—all in one place.” Slightly smoother.
-Appwrite is an open-source, all-in-one cloud development platform. Use built-in backend infrastructure and web hosting, all from a single place. +Appwrite is an open-source, all-in-one cloud development platform. Use built-in backend infrastructure and web hosting—all in one place.
234-234: Hyphenation/style nitPrefer “getting-started guides” (or “Get started with:”) for consistency.
-We’ve got a few get-started guides to help you kick off your projects quickly and smoothly: +We’ve got a few getting-started guides to help you kick off your projects quickly and smoothly:
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
💡 Knowledge Base configuration:
- MCP integration is disabled by default for public repositories
- Jira integration is disabled by default for public repositories
- Linear integration is disabled by default for public repositories
You can enable these sources in your CodeRabbit configuration.
📒 Files selected for processing (12)
src/routes/blog/post/appwrite-vs-auth0/+page.markdoc(1 hunks)src/routes/blog/post/appwrite-vs-cloudinary/+page.markdoc(1 hunks)src/routes/blog/post/appwrite-vs-firebase-vs-supabase-functions-comparison/+page.markdoc(1 hunks)src/routes/blog/post/best-ios-android-app-development-platforms/+page.markdoc(1 hunks)src/routes/blog/post/deploy-nextjs-app-to-appwrite-sites/+page.markdoc(1 hunks)src/routes/blog/post/gdpr-compliance-mobile-apps-alternative-firebase/+page.markdoc(1 hunks)src/routes/blog/post/open-source-firebase-alternative-messaging-fcm/+page.markdoc(1 hunks)src/routes/blog/post/open-source-firebase-alternative/+page.markdoc(1 hunks)src/routes/blog/post/open-source-startup-tools/+page.markdoc(1 hunks)src/routes/blog/post/planetscale-databases-alternative/+page.markdoc(1 hunks)src/routes/blog/post/role-based-access-control-with-appwrite/+page.markdoc(1 hunks)src/routes/blog/post/set-up-google-auth-appwrite-react/+page.markdoc(1 hunks)
✅ Files skipped from review due to trivial changes (1)
- src/routes/blog/post/open-source-startup-tools/+page.markdoc
🚧 Files skipped from review as they are similar to previous changes (10)
- src/routes/blog/post/role-based-access-control-with-appwrite/+page.markdoc
- src/routes/blog/post/deploy-nextjs-app-to-appwrite-sites/+page.markdoc
- src/routes/blog/post/appwrite-vs-firebase-vs-supabase-functions-comparison/+page.markdoc
- src/routes/blog/post/open-source-firebase-alternative/+page.markdoc
- src/routes/blog/post/set-up-google-auth-appwrite-react/+page.markdoc
- src/routes/blog/post/open-source-firebase-alternative-messaging-fcm/+page.markdoc
- src/routes/blog/post/appwrite-vs-cloudinary/+page.markdoc
- src/routes/blog/post/gdpr-compliance-mobile-apps-alternative-firebase/+page.markdoc
- src/routes/blog/post/planetscale-databases-alternative/+page.markdoc
- src/routes/blog/post/appwrite-vs-auth0/+page.markdoc
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (2)
- GitHub Check: build
- GitHub Check: tests
🔇 Additional comments (3)
src/routes/blog/post/best-ios-android-app-development-platforms/+page.markdoc (3)
230-233: Consistent Appwrite definition — LGTMCopy aligns with the standardized definition and reads cleanly in the Conclusion.
236-239: All quick-start links return HTTP 200 OK.
230-233: Canonical phrase appears once per post
Verified that the exact canonical copy is used exactly once in each blog post—including this one—so no duplicate occurrences were found.
What does this PR do?
Update's Appwrite definition to be consistent across blogs
Test Plan
View the changes
Related PRs and Issues
N/A
Have you read the Contributing Guidelines on issues?
Yes
Summary by CodeRabbit