---
title: "#sfra articles | Hashnode"
description: "Explore the latest #sfra articles, tutorials, and guides on Hashnode."
url: "https://hashnode.com/tag/sfra"
---

Tag

# #sfra

0 posts · 0 followers

[SapotaCorp](https://hashnode.com/@sapotacorpvn) · [Jul 12](https://hashnode.com/posts/b2c-commerce-sfra-controllers-and-middleware-request-shape/6a53c61aeb47841d58ddabe2)

### [B2C Commerce SFRA Controllers and Middleware: Request Shape](https://sapotacorpvn.hashnode.dev/b2c-commerce-sfra-controllers-and-middleware-request-shape?utm_source=hashnode&utm_medium=feed)

SFRA controllers replace SiteGenesis pipelines. Middleware composes the request lifecycle. The patterns are familiar from Express but the SFCC specifics decide whether your controller is two lines or two hundred.

7 min read · [sapotacorpvn.hashnode.dev](https://sapotacorpvn.hashnode.dev/b2c-commerce-sfra-controllers-and-middleware-request-shape?utm_source=hashnode&utm_medium=feed)

[SapotaCorp](https://hashnode.com/@sapotacorpvn) · [Jul 12](https://hashnode.com/posts/forms-in-sfra-validation-errors-and-persistence-patterns/6a53c4e441361a4465e6422e)

### [Forms in SFRA: Validation, Errors, and Persistence Patterns](https://sapotacorpvn.hashnode.dev/forms-in-sfra-validation-errors-and-persistence-patterns?utm_source=hashnode&utm_medium=feed)

Every B2C Commerce SFRA site has dozens of forms: login, register, checkout, account update, support. The form framework is opinionated and produces inconsistent results when developers fight it. The patterns that work are not in the docume

6 min read · [sapotacorpvn.hashnode.dev](https://sapotacorpvn.hashnode.dev/forms-in-sfra-validation-errors-and-persistence-patterns?utm_source=hashnode&utm_medium=feed)

[SapotaCorp](https://hashnode.com/@sapotacorpvn) · [Jul 12](https://hashnode.com/posts/models-and-viewdata-in-sfra-the-clean-data-flow/6a53c44e7370acb71858dadf)

### [Models and ViewData in SFRA: The Clean Data Flow](https://sapotacorpvn.hashnode.dev/models-and-viewdata-in-sfra-the-clean-data-flow?utm_source=hashnode&utm_medium=feed)

B2C Commerce SFRA separates the platform API from the template via a model layer. Done right, the templates render cleanly and the controllers stay thin. Done wrong, templates query the API directly and the codebase fragments.

6 min read · [sapotacorpvn.hashnode.dev](https://sapotacorpvn.hashnode.dev/models-and-viewdata-in-sfra-the-clean-data-flow?utm_source=hashnode&utm_medium=feed)

[SapotaCorp](https://hashnode.com/@sapotacorpvn) · [May 24](https://hashnode.com/posts/sfra-vs-sitegenesis-when-migration-is-worth-the-cost/6a127b6702c892c4d521d495)

### [SFRA vs SiteGenesis: When Migration Is Worth the Cost](https://sapotacorpvn.hashnode.dev/sfra-vs-sitegenesis-when-migration-is-worth-the-cost?utm_source=hashnode&utm_medium=feed)

A B2C Commerce org running on SiteGenesis works fine. Salesforce stopped active SG development in 2017. SFRA is the modern reference architecture. The migration cost is real and the timing decision is more nuanced than the marketing materia

7 min read · [sapotacorpvn.hashnode.dev](https://sapotacorpvn.hashnode.dev/sfra-vs-sitegenesis-when-migration-is-worth-the-cost?utm_source=hashnode&utm_medium=feed)