You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This EPIC contains some basic guidelines for tailwind styling when creating components and making them mobile responsive as well as definition of done for completing this EPIC. For example, it will highlight what text-size classes to use and what padding to use when creating components so that all the pages are consistent
When using breakpoints, I advise to take a mobile first approach where you should try to design with the mobile view in mind prior to the web view as most people are seeing our site from their phone.
Additionally, try to stay away from use the max-<breakpoint> class like max-sm: vs sm:. Default breakpoints, using just <breakpoint>:, handle all cases where the screen is that size OR larger. Thus, classes without any breakpoint prepended work by default for all screens and up, then get overrun by the breakpoint specific classes. This makes sure we have all of our screen sizes covered and maintain consistency with how the rest of the responsiveness in handled throughout the app.
DoD
List of remaining pages to make mobile responsive (as of 2/7/2025):
These are mainly in reference to the mobile view changes.
Padding
Horizontal
px-8 lg:px-40 - recommended to be used around the parent div of component
for hero section the parent div should use px-6 md:px-12 lg:px-32
Vertical - you can use whatever padding or margin you like here but ensure it is consistent with the spacing between the other components/ sections on the page
Typography
Section Heading - text-4xl lg:text-5xl
Heading 1 - text-3xl lg:text-4xl
Heading 2 - text-2xl
default text - text-xl
accent / less important text - text-lg
We try not to go any smaller than these sizes to ensure readability and accessibility
The text was updated successfully, but these errors were encountered:
Description
This EPIC contains some basic guidelines for tailwind styling when creating components and making them mobile responsive as well as definition of done for completing this EPIC. For example, it will highlight what text-size classes to use and what padding to use when creating components so that all the pages are consistent
When using breakpoints, I advise to take a mobile first approach where you should try to design with the mobile view in mind prior to the web view as most people are seeing our site from their phone.
Additionally, try to stay away from use the
max-<breakpoint>
class likemax-sm:
vssm:
. Default breakpoints, using just<breakpoint>:
, handle all cases where the screen is that size OR larger. Thus, classes without any breakpoint prepended work by default for all screens and up, then get overrun by the breakpoint specific classes. This makes sure we have all of our screen sizes covered and maintain consistency with how the rest of the responsiveness in handled throughout the app.DoD
List of remaining pages to make mobile responsive (as of 2/7/2025):
List of remaining large PRs needed for full mobile responsiveness:
Hoping to have all of these done by 02/13/2025
Tailwind Styling Guidelines
These are mainly in reference to the mobile view changes.
Padding
px-8 lg:px-40
- recommended to be used around the parent div of componentpx-6 md:px-12 lg:px-32
Typography
text-4xl lg:text-5xl
text-3xl lg:text-4xl
text-2xl
text-xl
text-lg
We try not to go any smaller than these sizes to ensure readability and accessibility
The text was updated successfully, but these errors were encountered: