Add new blog post about Remix 3

[ebenezerdon]

What does this PR do?

Test Plan

Related PRs and Issues

DRL-1802

Summary by CodeRabbit

• Documentation
  • Published a new blog post about Remix 3, covering architectural updates, core guiding principles, rendering model enhancements, data loading strategies, error handling, and developer experience improvements.

[coderabbitai]

Walkthrough

A new blog post file is added to the documentation at src/routes/blog/post/remix-3-whats-changing-and-why-it-matters/+page.markdoc. The file contains front-matter metadata and a complete article covering Remix 3 topics including motivations, architecture, design principles, rendering model, data loading, error handling, TypeScript support, documentation, developer experience, deployment, and forward-looking discussion. The content uses standard Markdoc/markdown formatting with code blocks and inline links. No functional application logic or code changes are introduced.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~5 minutes

• This is a pure content addition with no application code changes
• Review should focus on markdown syntax consistency and content accuracy
• Verify front-matter metadata formatting aligns with existing blog posts
• Confirm code block examples are syntactically correct

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately and concisely describes the main change: adding a new blog post about Remix 3, matching the file addition and content in the changeset.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch blog/remix-3-why-it-matters

---

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

• X
• Mastodon
• Reddit
• LinkedIn

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

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

src/routes/blog/post/remix-3-whats-changing-and-why-it-matters/+page.markdoc (1)

16-16: Consider adding a brief Node req/res vs Fetch API comparison.

While the article mentions that Remix 3 uses the Fetch API "instead of Node's proprietary req and res system" (line 16), and references Request and Response objects, it doesn't explain the practical differences. Developers familiar with Node.js might benefit from a line or two clarifying what this means operationally (e.g., Fetch API is standardized and available across runtimes, Node's req/res are specific to Node.js).

For example, after line 43, you could add context like: "Unlike Node's req and res objects which are specific to Node.js, the Fetch API's Request and Response are web standards available on all modern JavaScript runtimes."

Also applies to: 33-33, 43-43

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between f408b42 and 4494a70.

⛔ Files ignored due to path filters (1)

• static/images/blog/remix-3-whats-changing-and-why-it-matters/cover.png is excluded by !**/*.png

📒 Files selected for processing (1)

• src/routes/blog/post/remix-3-whats-changing-and-why-it-matters/+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). (3)

• GitHub Check: build
• GitHub Check: assets
• GitHub Check: tests

🔇 Additional comments (8)

src/routes/blog/post/remix-3-whats-changing-and-why-it-matters/+page.markdoc (8)

1-10: Frontmatter structure looks good.

All metadata fields are present and correctly formatted. The author ID ebenezer-don and category news are properly set.

---

36-36: Key past concerns have been addressed.

The article now includes mentions of TanStack, HTMX, and Zod, which were suggested in prior review rounds as relevant frameworks/libraries to reference. This improves context and credibility.

Also applies to: 64-64, 107-107

---

111-111: Developer resources and Appwrite mention integrated well.

The article links to preview demos, the official blog, and GitHub repository for readers to explore Remix 3 further—addressing the past feedback about providing actionable next steps. The deployment section also mentions Appwrite Sites alongside Netlify, Vercel, and edge workers, which provides good balance and acknowledges Appwrite's capabilities.

Also applies to: 126-126

---

93-94: Excellent articulation of server-side JS + client-side browser capabilities.

This passage clearly conveys the architectural shift and accessibility benefits: "Remix runs JavaScript on the server but leverages existing browser capabilities on the client side." This directly addresses a past concern about explaining the server/client split early and prominently. Good placement in the data loading section.

---

74-89: Handler example is clear and helpful.

The GET/POST handler pattern demonstrates the loader/action concept effectively. The example shows both rendering on GET and form handling on POST, which illustrates the before/after mindset shift from Remix 2. Good choice to include actual code here.

---

130-136: Trade-offs section is balanced and realistic.

The article acknowledges real friction points (losing React ecosystem, learning curve, manual updates) without being defensive. This builds credibility and helps readers make informed decisions. The counter-arguments (less complexity, less JS on client, better performance) are compelling and proportionate.

---

6-6: Cover image file verified and accessible.

The file exists at ./static/images/blog/remix-3-whats-changing-and-why-it-matters/cover.png, which correctly resolves to the frontmatter path /images/blog/remix-3-whats-changing-and-why-it-matters/cover.png in the application.

---

111-111: I need to verify the remaining URL mentioned in the review comment:

All external links are valid and accessible.

The verification confirms that all referenced URLs return successful HTTP 200 responses:

• https://remix.run/blog/wake-up-remix ✓
• https://remix.run/blog/remix-jam-2025-recap ✓
• https://remix.run/blog (main blog) ✓
• https://github.com/remix-run/remix ✓

The links are suitable for citation and unlikely to change soon.