Development: Update client documentation to use standalone components (…

…#8678)

docs/dev/guidelines/client.rst

@@ -35,6 +35,12 @@ Some general aspects:
 2. Components
 =============
 
+In our project, we promote the creation of standalone components instead of using Angular modules. A standalone component is a self-contained unit that encapsulates its own logic, view, and styles. It doesn't directly depend on its parent or child components and can be reused in different parts of the application.
+For existing components that are not standalone, we should aim to migrate them step by step. This migration process should be done gradually and carefully, to avoid introducing bugs. It's recommended to thoroughly test the component after each change to ensure it still works as expected.
+Standalone components can be generated with the Angular CLI using ``ng g c <component-name> --standalone``.
+
+More info about standalone components: https://angular.dev/guide/components/importing#standalone-components
+
 1. 1 file per logical component (e.g. parser, scanner, emitter, checker).
 2. files with ".generated.*" suffix are auto-generated, do not hand-edit them.