Skip to content

Migrate to Tailwind #6

@aryanprince

Description

@aryanprince

Summary

Would you be open to migrating this codebase to Tailwind? There are so many benefits to it, can maintain the exact same styling patterns (the Apple-like design) - while having much better DX.

Why

  • Better DX
    • No need to jump around diff files
    • No need to create new CSS classes for adding styles
    • Way better consistency (currently some styles use class selectors like .card while others use semantic HTML elements like nav)
    • And so much more...

For example: If you wanted to update the styling for the main homepage, you gotta edit index.astro. Except, layout related styling is now in Layout.astro. Lotta jumping back and forth now to figure out which classes affect which pages now.

  • Way better responsive design

Lot of manual work to create all the different responsive breakpoints, and adding custom classes to it. Tailwind makes all of this easier (and better).

  • Performance wins (Tailwind does a lotta magic under the hood)

If Yes

I can help with the migration if you're down to do this.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions