Skip to content

Conversation

@Veera-mulge
Copy link
Contributor

@Veera-mulge Veera-mulge commented Oct 3, 2025

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.)

Summary by CodeRabbit

  • Documentation
    • Added "Best Free Static Website Hosting": six-provider comparison with features, pricing, pros/cons, expanded Appwrite Sites coverage and FAQ on deployments, free tiers, SSR/SSG, edge features, and vendor-lock considerations.
    • Added "Best Push Notification Strategies": overview, four engagement approaches, setup/workflow guidance, and comprehensive FAQ.
    • Expanded FAQs in the Netlify vs Vercel vs Amplify vs Appwrite Sites article with clearer explanations.

@coderabbitai
Copy link
Contributor

coderabbitai bot commented Oct 3, 2025

Walkthrough

Adds two new blog posts at src/routes/blog/post/best-free-static-website-hosting/+page.markdoc and src/routes/blog/post/best-push-notification-strategies/+page.markdoc containing full article content and frontmatter. Expands FAQ answers (questions 1–7) in src/routes/blog/post/netlify-vs-vercel-vs-amplify-vs-appwrite-sites/+page.markdoc. No code logic, control flow, exported APIs, or public declarations were changed.

Possibly related PRs

Suggested reviewers

  • tessamero
  • LauraDuRy
  • ebenezerdon

Pre-merge checks and finishing touches

❌ Failed checks (1 inconclusive)
Check name Status Explanation Resolution
Title Check ❓ Inconclusive The provided title “New faq blogs” is too vague and generic to clearly convey the content or scope of the changes since the PR actually adds three distinct FAQ-style blog posts on static hosting, push notifications, and provider comparisons. Please update the title to clearly reflect the key content of the PR, for example “Add three FAQ blog posts on static site hosting, push notification strategies, and provider comparisons.”
✅ Passed checks (2 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Docstring Coverage ✅ Passed No functions found in the changes. Docstring coverage check skipped.
✨ Finishing touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch new-faq-blogs

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 36ef28a and 28791bc.

📒 Files selected for processing (2)
  • src/routes/blog/post/best-free-static-website-hosting/+page.markdoc (1 hunks)
  • src/routes/blog/post/best-push-notification-strategies/+page.markdoc (1 hunks)
⏰ 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

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

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

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 3

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 58d22bb and bce7c9d.

⛔ Files ignored due to path filters (2)
  • static/images/blog/best-free-static-website-hosting/cover.png is excluded by !**/*.png
  • static/images/blog/best-push-notification-strategies/cover.png is excluded by !**/*.png
📒 Files selected for processing (3)
  • src/routes/blog/post/best-free-static-website-hosting/+page.markdoc (1 hunks)
  • src/routes/blog/post/best-push-notification-strategies/+page.markdoc (1 hunks)
  • src/routes/blog/post/netlify-vs-vercel-vs-amplify-vs-appwrite-sites/+page.markdoc (1 hunks)
⏰ 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 (9)
src/routes/blog/post/netlify-vs-vercel-vs-amplify-vs-appwrite-sites/+page.markdoc (1)

137-162: LGTM! FAQ answers are clear and informative.

The expanded FAQ responses effectively compare Appwrite Sites to competing platforms (Vercel, Netlify, AWS Amplify) and clearly communicate key differentiators: open-source nature, self-hosting capability, integrated backend services, and Git-based deployment support.

src/routes/blog/post/best-push-notification-strategies/+page.markdoc (4)

1-11: LGTM! Frontmatter is correctly formatted.

The frontmatter includes all required fields for a blog post with appropriate values.


13-44: LGTM! Content is well-structured and informative.

The introduction, overview, and engagement strategies sections are clear, concise, and provide actionable guidance for developers implementing push notifications.


46-99: LGTM! FAQ section is comprehensive.

The FAQ effectively addresses common questions about push notifications, Appwrite's capabilities, provider support, and setup process. The technical explanations are accurate and the comparison with Firebase is balanced.


19-98: All documentation links are valid
All referenced doc paths exist under src/routes/docs/products/messaging.

src/routes/blog/post/best-free-static-website-hosting/+page.markdoc (4)

19-27: LGTM! Comparison table is well-structured.

The feature comparison table provides a clear, at-a-glance overview of the six hosting providers with relevant criteria for developers choosing a platform.


28-51: LGTM! Appwrite Sites section is comprehensive.

The section effectively highlights Appwrite Sites' unique value proposition of combining frontend hosting with integrated backend services. The pros/cons are balanced and accurate.


52-173: LGTM! Provider sections are well-researched.

All provider sections (Vercel, Render, Netlify, GitHub Pages, Cloudflare Pages) present accurate information about features, pricing, and trade-offs. The pros/cons tables provide balanced assessments.


179-204: Verify documentation file existence for all referenced /docs paths

Ran searches but found no matching .md/.mdx/.markdoc files under docs/; please confirm the following paths resolve to actual files (with appropriate extensions) and update links if needed:

  • docs/products/sites/rendering/ssr
  • docs/products/auth
  • docs/products/databases
  • docs/products/sites/domains
  • docs/advanced/security
  • docs/products/sites/quick-start/react
  • docs/products/sites
  • docs/products/sites/previews

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 2

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between bce7c9d and 2596d5b.

📒 Files selected for processing (2)
  • src/routes/blog/post/best-free-static-website-hosting/+page.markdoc (1 hunks)
  • src/routes/blog/post/best-push-notification-strategies/+page.markdoc (1 hunks)
🚧 Files skipped from review as they are similar to previous changes (1)
  • src/routes/blog/post/best-push-notification-strategies/+page.markdoc

@atharvadeosthale atharvadeosthale merged commit f92cf20 into main Oct 3, 2025
4 checks passed
@atharvadeosthale atharvadeosthale deleted the new-faq-blogs branch October 3, 2025 21:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants