Skip to content

Rethink packages structure #2237

Description

@hasparus

When you get started with Theme UI, it's not trivial to know what feature is powered by what package, as most of the functionalities we provide are opt-out not opt-in. This has led to confusion many times.

I think we should address it by looking at how people use Theme UI in production and redesigning how the features are split to match it.

Loose notes:

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions