The Crypto Native Portal, an app that creates a mechanism to financially acknowledge the micro contributions of Open Source collaborators along with tools that promote effective governance.
3
stars
1
forks
source link
[Refactor] Folder structure : Refactor the code base to apply the new folder structure #288
In components, we can have a structure like this:
Secion: they are the main part of a page, usualy section are not thinked to be reusable, their main goal is to split the page into small peace of content. Section are grouped into page folder. So we can identify the page and the section of the page.
Sections are component that are alowed to have logic inside. So they can process data like fetching, using composable or accessing the store.
UI: They are the most reusable component, they are the basic component like button, input, modal, etc.
And we can create a folder for each type of component, like Form, Icons etc.
Acceptance Criteria
Each Page has his section folder
### Tasks
- [x] Team View
- [x] Single Team View
- [x] Transactions
Description
We need to apply the new folder structure so we can have a code base more structured
Here is an example of how we can structure our components: Idea of structure
In components, we can have a structure like this: Secion: they are the main part of a page, usualy section are not thinked to be reusable, their main goal is to split the page into small peace of content. Section are grouped into page folder. So we can identify the page and the section of the page. Sections are component that are alowed to have logic inside. So they can process data like fetching, using composable or accessing the store.
UI: They are the most reusable component, they are the basic component like button, input, modal, etc. And we can create a folder for each type of component, like Form, Icons etc.
Acceptance Criteria
Each Page has his section folder