chore(setup): decide on folder structure and naming

cloudoperators / juno

Monorepo for the Juno microfrontend framework, microfrontend apps, design system and component library

Apache License 2.0

2 stars 0 forks source link

chore(setup): decide on folder structure and naming #39

Closed edda closed 4 weeks ago

edda commented 1 month ago

Decide on and implement the folder structure we want to use within the Juno repo for the projected contents, i.e. packages that can be libs, apps, or MFEs.

belongs to #40
[x] Decide folder structure
[x] Decide folder naming conventions
[x] Create a markdown file

andypf commented 1 month ago

We can keep the directory structure flat and include the scope and type in the name of the asset: Example: elektra-mfe-compute or juno-lib-ui-components. I really think we should rename juno-ui-components to ui-components.

All assets should be placed under packages

packages:
  - elektra-mfe-compute
  - juno-lib-ui-components
  - juno-lib-communicator

It remains to be decided whether we want to reflect the scope and type in package.json and also enter elektra-mfe-compute under name?

andypf commented 1 month ago

Naming decision: https://github.com/cloudoperators/juno/blob/main/docs/decision_naming_schema.md