Skip to content

Use case-led content #32

@elisechant

Description

@elisechant

We know that there is no one-size-fits-all monorepo solution and that the current site is not serving this well.

In response, we would like to reform site content so that it is use case-led. We will deliberately limit scope to what has been useful at Thinkmill.

These will be the initial scenarios:

  1. I want to build a product
  2. I want to build a product with a design system
  3. I want to use packages outside of the monorepo
  4. I want to build an open source library
  5. I want to bring existing packages in to a monorepo

Each scenario will document relevant patterns and tooling.

This narrowing, will allow us to provide clients who want to do a particular thing, to a relevantly scoped resource. Resources should have enough detail to answer questions "what should you expect from a monorepo" and "how we do it".

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions