Skip to content

Rewrite Monorepo docs #2537

@timofei-iatsenko

Description

@timofei-iatsenko

I have this in the back of my mind for a looong time, need to put it as a task and do some day, here are topics i would like to cover:

  • Without Publishable Packages (apps/app-a, apps/app-b, packages/button, packages/dialog, etc)
    Possible strategis:
    • One catalog per app
    • Catalog per package + merging
  • With publishable Packages
    • Avoid having translations in packages if possible, pass copies as Props
    • If not possible:
      • Catalog per package + merging
      • One catalog per whole UI Components library

The thing is that "Monorepo" could be very diffrent from project to project. We need to brainstorm how to structure this information, so the user would find a suitable information without reading unrelated parts.

So something like flow diagram, or wizard:

"Do you publish your packages?" - Yes/No -> go to paragraph 2 or 3

all above is a raw dump of my thoughts, to be improved later

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