sts-sponsors team mailing list archive
-
sts-sponsors team
-
Mailing list archive
-
Message #07331
[Merge] ~petermakowski/maas-site-manager:add-css-readme-section into maas-site-manager:main
Peter Makowski has proposed merging ~petermakowski/maas-site-manager:add-css-readme-section into maas-site-manager:main.
Commit message:
docs: add CSS section to frontend readme
Requested reviews:
MAAS Lander (maas-lander): unittests
MAAS Committers (maas-committers)
For more details, see:
https://code.launchpad.net/~petermakowski/maas-site-manager/+git/site-manager/+merge/441653
--
Your team MAAS Committers is requested to review the proposed merge of ~petermakowski/maas-site-manager:add-css-readme-section into maas-site-manager:main.
diff --git a/frontend/README.md b/frontend/README.md
index 46949ed..d513d9c 100644
--- a/frontend/README.md
+++ b/frontend/README.md
@@ -37,6 +37,14 @@ yarn run dev
## Project conventions
+## CSS
+
+### Mobile-first approach
+
+We first write CSS styles specifically for mobile devices, and then progressively enhance them for larger screen sizes using min-width media queries.
+
+Single and consistent direction of media queries (min-width) makes the code easier to read and maintain.
+
## Testing
We use [Playwright](https://playwright.dev/) for end-to-end tests and [Vitest](https://vitest.dev/) for unit/integration tests. We prefer integration testing over unit testing as we focus on user-centric testing and avoid testing implementation details. That makes changes and refactoring easier and helps ensure that things continue to work as expected for the end user.