Your question is like asking how to build a simple two-stroke engine. While the pieces may not be numerous, the process of designing and assembling them requires a significant amount of knowledge. That's likely why someone downvoted your question - asking more specific questions, sharing your research, attempts, and challenges faced can lead to more helpful responses.
There are plenty of tutorials available on angular, but finding one that caters to your specific needs can be more challenging. Front-end programming is unique for each project, so starting with a basic tutorial like the main Angular one can provide a solid foundation. Even if you won't use everything in your current project, it's a great way to grasp the basics and then apply them to your specific application.
General information:
Angular allows you to create webapps for hosting on domains.
A project consists of multiple components that need to be included in an app.modules.ts file (automatically done by angular-cli).
Components can be placed on different URLs managed by a router (app.routing.ts, also generated automatically) or nested within each other. Each component requires an HTML template to dictate its display. You can utilize attributes from the component class directly in the HTML.
While each walkthrough screen doesn't necessarily need its own route and component, Angular's strength lies in creating a dynamic single page that adapts to user input. Although most webapps have multiple pages that can change reactively, you may only require a single page for your project. (Consider looking into Single Page Applications - SPA)
Now, let's break down the components in that Slack tutorial. It includes a background, a static 'skip' button, 1 or 2 dynamic arrows, and a sequence of dots at the bottom. You might want a single component with a list of backgrounds, using *ngIf for the arrows, *ngFor, and the router for the skip button.
Alternatively, instead of a list of backgrounds, you could have a main component with subpage components using mat-tab-groups. This approach simplifies the page transitioning process.