A frontend architecture decides what the server renders, what the browser owns, and which state must survive navigation. These decisions affect accessibility, load cost, failure handling, and the team's ability to change one screen without breaking another.
Topics in this track
- Component Boundaries and State Ownership — Keep source records, temporary input, and derived display values in distinct places.
- Browser Routing and History State — Keep client navigation aligned with a route the server can open directly.
- Static, Server-Rendered, and Client-Rendered Pages — Choose a rendering boundary from data freshness, interaction, and failure needs.
- Locale and Time-Zone Boundaries — Store an unambiguous instant and format it for the reader at the edge.
Connect with existing lessons
DOM events: enhance a working control without losing its baseline; HTML Tutorial; CSS Tutorial.
Other broad tracks
Backend and API Systems; Data Persistence; Media and Live Updates; Offline and Device Capabilities; Deployment and Scale; Content Discovery and Structure.
Practice path
After the four lessons, build Project: paginated inspection feed with safe writes and take Web Development: offline and delivery contracts quiz.
Further connections
Internationalization and Content Delivery.
Further connections
Typed Frontend and Component Platform.
Further connections
CSS Layout and Interface Systems; Browser Execution and Resource Lifecycle.