Loading
Topic
Component ownership, dependency boundaries, state placement, routing, and maintainable frontend composition.
Practice items tagged with Frontend Architecture.
Separates projected caller-owned content from a component's own view and explains when queries are justified.
Explains contextual sanitization and treats bypass APIs as narrow security-review decisions rather than general encoding helpers.
Connects environment and element injectors to instance lifetime, overrides, lazy routes, and accidental state isolation.
Chooses template-driven, typed reactive, or experimental Signal Forms based on workflow complexity and stability needs.
Uses ownership, inputs, outputs, rendering responsibility, and dependency scope to define maintainable standalone components.
Uses production build output, explicit budgets, dependency analysis, and meaningful lazy boundaries instead of arbitrary size cuts.