State is the data your app remembers: a counter, a selected item, a shopping cart. Signals are Angular's built-in way to hold that data and tell the framework exactly what changed, so only the parts of the screen that depend on it need to update.
It starts with the signal() function for writable state, with set and update to change it. From there it covers computed() for values derived from other signals, which recalculate only when their inputs change, and linkedSignal() for state that resets when another signal changes. Putting signals inside a service, as covered in the Services & Dependency Injection module, gives you simple shared state across components. It's also worth knowing that effect() runs side effects when signals change, and that libraries like the NgRx SignalStore build on signals for larger apps.
Signals are a newer part of Angular, so the videos here are fairly recent. Some may show decorators like @Input where newer code uses signal-based inputs, but the core ideas are the same. Watch the lessons in order, then continue on to Testing, Build & Deployment.
A step-by-step beginner tutorial on managing reactive state with signal() and computed(), plus linkedSignal().
Covers Angular Signals as a way to manage state and keep your UI in sync with data changes.
Explains what computed signals are and how they give you reactive values derived from other signals.
Shows how computed signals model derived state in modern Angular, expressing relationships between pieces of state.