Skip to content

Commit dc3a137

Browse files
committed
add clarity to global css example; fix formatting
1 parent 8ce7a11 commit dc3a137

File tree

1 file changed

+6
-6
lines changed

1 file changed

+6
-6
lines changed

docs/architecture/clients/index.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -10,10 +10,10 @@ and a single [Git repository](https://github.com/bitwarden/clients).
1010

1111
The mono-repository root directory contains three main folders.
1212

13-
- `apps` - Our different application specific code, consists of `web`, `browser`, `desktop` and
13+
- `apps`: Our different application specific code, consists of `web`, `browser`, `desktop` and
1414
`cli`.
15-
- `bitwarden_license` - Bitwarden Licensed version of the web vault.
16-
- `libs` - Shared code between the different applications.
15+
- `bitwarden_license`: Bitwarden Licensed version of the web vault.
16+
- `libs`: Shared code between the different applications.
1717

1818
## Libs
1919

@@ -51,8 +51,8 @@ concerned with bootstrapping the application and consuming and configuring code
5151

5252
Any code in the `apps/` that doesn't have a tight coupling with the client can be moved into a lib:
5353
if an exported member is wholly dependent on other libs but not `apps/`, it can likely be moved to a
54-
lib itself. (More concretely, this bars components that rely on global client-specific CSS, but not
55-
components built with Tailwind and the CL.)
54+
lib itself. (More concretely, this bars components that rely on global client-specific CSS but not
55+
components built with Tailwind and the CL — from being included in a lib)
5656

5757
> Having a dedicated library project is a much stronger boundary compared to just separating code
5858
> into folders, though. Each library has a so-called "public API", represented by an index.ts barrel
@@ -64,7 +64,7 @@ An existing example of this pattern is `@bitwarden/components`:
6464

6565
- It is consumed by multiple apps and other libs
6666
- It manages a clear public and private API boundary through its barrel file
67-
- Code ownership is clear--the CL team only owns the files within `libs/components`
67+
- Code ownership is clearthe CL team only owns the files within `libs/components`
6868
- The CL team can make independent decisions around internal folder structure and code style
6969

7070
As part of this process, we are also investigating utilizing additional tooling (such as Nx) to make

0 commit comments

Comments
 (0)