Beginning Angular
Angular is a framework for building applications, not pages, and it brings a lot with it: a CLI, a component model, signals, dependency injection, routing, a template compiler, and opinions about all of them. Learned piecemeal from tutorials, that adds up to an application nobody on the team understands the same way.
This course lays the foundation together, as a team. We place Angular in context, including what single-page applications are for and what problem change detection solves, then work through the building blocks: components and templates, signals, communication between components, pipes, directives, services, routing, and talking to APIs. Along the way we set up the development environment and the tooling a team needs to build, lint, and test the application in a pipeline.
Who it’s for
Developers who will create or contribute to Angular applications in an enterprise. It’s a beginning Angular course, but not an introduction to programming: you should already write software in a language like C#, Java, or Go, and have some understanding of the technologies behind a web application. The self-paced Angular pre-work helps you find and fill any gaps before class.
How it runs
Four days, live and online, 9:30 AM to 5:00 PM ET. Lecture and demonstration, short practice exercises right after each concept, two longer labs, and brief review and design sessions with the whole class. It’s not a PowerPoint death march: expect to code along and to talk. You’ll get a development virtual machine for the duration, so there’s nothing to install; a good microphone, a webcam, and a second monitor make a real difference. Reference material stays available after class, including updates made after you’ve graduated.
What you’ll be able to do
- Explain where Angular fits, and what it’s doing for you when the screen updates.
- Create, configure, and run an Angular application with the Angular CLI.
- Set up VS Code, Prettier, and ESLint, and manage dependencies with npm the way a team should.
- Build components, directives, pipes, and services, and know which one a problem calls for.
- Manage component state with signals.
- Organize source code by conventions a team can follow.
- Read from and write to APIs with the
HttpClientand the resource APIs. - Build, lint, and test an application so it’s ready for a CI/CD pipeline.