> For the complete documentation index, see [llms.txt](https://docs.aurelia.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.aurelia.io/getting-started/extended-tutorial/step-1-project-setup.md).

# Step 1: Project setup + app shell

Set up Project Pulse, enable the router, and build the shared app shell.

In this step you will create the project, enable the router, and build a shared layout component.

## 1. Create the project

```bash
npx makes aurelia
# Name: project-pulse
# Select TypeScript
cd project-pulse
npm run dev
```

## 2. Enable the router and active link styling

Update `src/main.ts` to register the router and configure an active class for navigation links:

```typescript
import Aurelia from 'aurelia';
import { RouterConfiguration } from '@aurelia/router';
import { MyApp } from './my-app';

Aurelia
  .register(RouterConfiguration.customize({ activeClass: 'is-active' }))
  .app(MyApp)
  .start();
```

Any `<a load="...">` link will now get the `is-active` class when the route is active.

## 3. Create the app shell

Create the folders `src/components` and `src/pages` if you do not have them yet.

Create `src/components/app-shell.ts`:

```typescript
export class AppShell {}
```

Create `src/components/app-shell.html`:

```html
<div class="shell">
  <header class="shell__header">
    <div class="shell__title">
      <au-slot name="title">Project Pulse</au-slot>
    </div>
    <div class="shell__actions">
      <au-slot name="actions"></au-slot>
    </div>
  </header>

  <main class="shell__body">
    <au-slot></au-slot>
  </main>
</div>
```

Next step: [Step 2: Routing + nested layouts](/getting-started/extended-tutorial/step-2-routing-and-layout.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.aurelia.io/getting-started/extended-tutorial/step-1-project-setup.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.