# Where the frontend lives

A step of the [Cloud application](https://gradus.kazet.blog/tree/cloud-application) tree on Gradus, in the Frontend area: Second app, UI, browser tests.

Page: https://gradus.kazet.blog/tree/cloud-application/step/choose-repo-layout

Decide whether the frontend is a workspace in this repository or a repository of its own, and write it down. The second answer is where cross-repository knowledge enters.

Usually comes after: [Data access layer & seed data](https://gradus.kazet.blog/tree/cloud-application/step/data-access-layer).

Leads to: [A workspace in the same repository](https://gradus.kazet.blog/tree/cloud-application/step/frontend-workspace), [A second repository](https://gradus.kazet.blog/tree/cloud-application/step/frontend-repository), [Choose a frontend approach](https://gradus.kazet.blog/tree/cloud-application/step/choose-frontend).

## Prompt for your AI assistant

```
Read docs/index.md and everything under docs/product and docs/decisions. Help me decide where this product's frontend should live: a workspace in this repository or a second repository. Compare the two for a single developer with an AI assistant: shared tooling and one CI against independent deploys and a knowledge base per repository. Recommend one and why, then write the next docs/decisions record for the repository layout with context, options, decision and consequences. Create nothing yet.
```

Every step of the tree: https://gradus.kazet.blog/tree/cloud-application/llms.txt