Skip to content

Commit f92310a

Browse files
committed
chore: cleanup
1 parent c789c14 commit f92310a

File tree

1 file changed

+4
-3
lines changed

1 file changed

+4
-3
lines changed

docs/contributing/frontend.md

Lines changed: 4 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -23,7 +23,7 @@ You can run the UI and access the Coder dashboard in two ways:
2323
In both cases, you can access the dashboard on `http://localhost:8080`. If using
2424
`./scripts/develop.sh` you can log in with the default credentials.
2525

26-
### Default Credentials: `admin@coder.com` and `SomeSecurePassword!`.
26+
> **Default Credentials:** `admin@coder.com` and `SomeSecurePassword!`.
2727
2828
## Tech Stack Overview
2929

@@ -82,7 +82,7 @@ Page components are the top-level components of the app and reside in the
8282
`src/pages` folder. Each page should have its own folder to group relevant
8383
views, tests, and utility functions. The page component fetches necessary data
8484
and passes to the view. We explain this decision a bit better in the next
85-
section.
85+
section which talks about where to fetch data.
8686

8787
> ℹ️ If code within a page becomes reusable across other parts of the app,
8888
> consider moving it to `src/utils`, `hooks`, `components`, or `modules`.
@@ -243,7 +243,8 @@ module would only make sense in the Coder codebase.
243243
- Used in multiple places
244244
- Good Examples: `Provisioner`, `DashboardLayout`, `DeploymentBanner`
245245

246-
Do not assume existing components and modules have been categorized correctly.
246+
Our codebase has some legacy components that are being updated to follow these
247+
new conventions, but all new components should follow these guidelines.
247248

248249
## Styling
249250

0 commit comments

Comments
 (0)