Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Refactor the application structure #260

Open
viktor-yakubiv opened this issue Apr 14, 2020 · 0 comments
Open

Refactor the application structure #260

viktor-yakubiv opened this issue Apr 14, 2020 · 0 comments
Labels
♻️ refactoring Restructuring, cleaning up

Comments

@viktor-yakubiv
Copy link
Member

viktor-yakubiv commented Apr 14, 2020

The desired structure is:

  • elements@oacore/design with patches
  • modules – complex components based on elements
    • at the moment I see depositing, content
  • templates – individual user activities we have such as deposit-dates, content, overview and so on, based on modules
  • pages – real routes mapped to templates and connected to global application state
  • app – global application setup

Three from the top should be state-independent, the last 2 can be dependent on the state (store) and Next.

The pages are dependent on Next anyway. The app could be split to Next-dependent and independent one. However, with Next 9.3 we can have it independent at all.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
♻️ refactoring Restructuring, cleaning up
Projects
None yet
Development

No branches or pull requests

1 participant