Skip to content
This repository was archived by the owner on Oct 5, 2024. It is now read-only.

Grouping components by modules or "areas of concern" #41

@Aztriltus

Description

@Aztriltus

For the modules, it feels like it contains components from multiple "areas of concern".

What do you think of creating modules so they are better grouped together? I'm not sure if "deploy" is a good name for a module, but it could contain the components that is used for the deploy page. E.g. src/deploy/CreateNFTCard, src/deploy/DeployedSiteCard, etc. Then in the future if it gets bigger, we could further divide them in the deploy folder. I think it could make it easier to find the components, and also we can add other things like hooks, functions that are only reused within that module.

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