# Code maintenance DREAM-823 - Reframe the frontend style guide for Hotwire

Project: Stream Design System
Status: in specification
URL: https://community.openproject.org/work_packages/DREAM-823

## OPEN POINTS

_No work packages_

## Subtasks

_No work packages_

## Details

| Attribute | Value |
| --- | --- |
| Assignee |  |
| Accountable |  |
| Designer |  |
| Developers |  |
| Requires doc change | No |
| Date |  |
| Priority | Medium |
| Target versions |  |
| Sprint |  |
| Backlog bucket |  |
| Module |  |
| Accessibility | No |
| List |  |
| Labels |  |

## Estimates and progress

| Attribute | Value |
| --- | --- |
| Work |  |
| Remaining work |  |

## Description

## Context

`docs/development/style-guide/frontend/README.md` describes the frontend as an Angular application. Its "Development patterns" section opens with "Angularized — OpenProject follows the Angular style guide", and the patterns that follow are Angular ones: container and presentational components, unidirectional data flow explained through Angular's change detection, and an Angular Material button as the worked example.

Angular is now the legacy tree. New development uses Hotwire — Turbo and Stimulus — with server-rendered HTML and Primer via ViewComponent. A contributor reading this guide today is being pointed at the architecture we are migrating away from, with nothing describing the one we are migrating towards.

Related staleness in the same file was already corrected under https://community.openproject.org/wp/DREAM-821: it claimed the project follows the AirBnB JavaScript style guide, which is not installed and is not referenced by `eslint.config.mjs`, and it linked the retired `angular.io` domain. The code-format section now points at the ESLint configuration that actually enforces format.

## Goal

Make the frontend style guide describe the architecture the project is moving towards, and be explicit about which parts apply only to the legacy Angular tree.

## Scope

Open questions to settle first, since they change the shape of the work:

- Does the Angular pattern material stay, clearly marked as legacy, or move into a separate legacy document?
- What replaces it for Hotwire? Stimulus controller conventions, Turbo stream usage and the Primer/ViewComponent boundary are currently undocumented as *patterns*, though `frontend/doc/TESTING.md` covers how to test controllers.
- How much of the general material — declarative style, immutability, clean code, command/query separation — is framework-neutral and worth keeping as-is?
- Is BEM still the CSS convention now that Primer supplies components?

## Notes

The house code style evolved organically and is enforced rather than written down. Standardising it further is worth considering as part of this, but is a separate decision.
