Using Remix Actions as Your Only Form-Handling Layer: An Architecture Note
An architecture note on using Remix route actions as your only mutation layer: requirements, minimal design, trust boundaries, operational checks, and when to deviate.
ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
An architecture note on using Remix route actions as your only mutation layer: requirements, minimal design, trust boundaries, operational checks, and when to deviate.
Learn how to implement Remix loaders to eliminate client-side loading waterfalls, secure server-side secrets, and manage the boundary between server data and client UI.
Learn how to serve a web app to Internet Explorer 10 using only standards‑mode controls, limited CSS3, and server‑side enforcement, with concrete checks and failure‑mode guidance.
An architecture note describing how to use IE10's Pointer Events API for unified mouse, touch, and pen input, including requirements, minimal design, trust boundaries, checks, failure modes, and when the design would change.
Learn how to build a secure, testable KrakenJS middleware stack that validates input, authenticates users, and safely calls your controller. The article covers requirements, trust boundaries, logging, error handling, and when to refactor for scale.
Learn how to use Sulu CMS Zones to create flexible, editor-driven layouts that decouple content structure from presentation using Symfony and React.