Documenting and organizing the team to consider architecture questions

[victordelval]

As discussed at the last Architecture Review meeting (July 7, 2022), an initial task is created to address design and architecture issues around the Regen Web ecosystem (regeb-web monorepo) in an organized and unified manner.

There are several issues, at various levels.

At a global level, thinking about decoupling, reuse and scalability, it is necessary to improve the design of:

• packages
• Applications

At a specific level, possible packages:

• Web Components (refine design system, pure components, isolate MUI)
• Ledger (on-chain) / Schemas
• Wallet
• DB (off-chain) / Schemas
• Schemas

At a specific level, applications:

• Registry
• Regen Lands

Regarding the applications:

• domain-based architecture and layered separation

• considering migrating to production-ready React frameworks (Remix and Next.js)

[victordelval]

Some existing related tasks:

• Create a ledger module to encapsulate related logic
• POC on documentation and diagramming for a registry use case

[victordelval]

Meeting notes:

• https://www.notion.so/regennetwork/Interfaces-Engineering-Check-in-e0ccc3ba0e3144289faf18794feaaac3