Transition from 'module.css' to Styled Components

[PublicRouter]

Complete front-end transition from using module.css files to Styled Components. This change aims to improve maintainability, consistency, and scalability of our styling approach across the project.

This applies to COMPONENTS only, we will still have global index.css and app.css files for styling on a higher scope.

All ongoing development should consider this transition.

Objectives

• Consistency in Styling: Unify the styling approach to ensure a consistent look and feel across the application.
• Improved Developer Experience: Leverage the advantages of Styled Components, such as enhanced theming capabilities and easier component-based styling.
• Codebase Clean-up: Remove redundant CSS code and streamline our styling files.

[caiodutra08]

Hi @PublicRouter and SigVerify team,

I came across with this "issue" and I'm interested in contributing to this effort. I have experience with Styled Components and believe I can help improve the maintainability and consistency of the project's styling.

I understand the objectives are to ensure consistency in styling, improve developer experience, and clean up the codebase. I'm ready to start working on this and would appreciate any specific guidelines or areas of the project you'd like me to focus on first.

Looking forward to collaborating on this!

Best, caiodutra08

[rosseti]

@PublicRouter @caiodutra08 I believe the first step would be to try running the project on your local machine to understand its functioning. Then, fork it into your namespace. After that, you can start making modifications, and once completed, submit a pull request for review. I believe any assistance here is greatly appreciated.

[PublicRouter]

Yes this would be great! All assistance is greatly appreciated. I just made a recent push to main with a lot of updated components converted to styled components but all help is welcome!

Appreciate all the interest in the project. In the meantime I am hammering out a mvp schema for the database tables for storing and manipulation of documents and then xumm and xrpl integration hopefully soon after!

On Mon, Nov 27, 2023 at 1:54 PM Andrei @.***> wrote:

@PublicRouter https://github.com/PublicRouter @caiodutra08 https://github.com/caiodutra08 I believe the first step would be to try running the project on your local machine to understand its functioning. Then, fork it into your namespace. After that, you can start making modifications, and once completed, submit a pull request for review. I believe any assistance here is greatly appreciated.

— Reply to this email directly, view it on GitHub https://github.com/LedgerIntegrations/SigVerify/issues/6#issuecomment-1828501194, or unsubscribe https://github.com/notifications/unsubscribe-auth/AZI4V3RMM67UR7JINEDGDTDYGTVYXAVCNFSM6AAAAAA7HN7M4CVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMRYGUYDCMJZGQ . You are receiving this because you were mentioned.Message ID: @.***>

[caiodutra08]

Hey, it's been some months, and finally I free code time. Can I finish what's left and even if it's needed apply some patterns for better scalability of the project? Feel free to contact me in any of theses social medias. @caiodutra08 in any platform.