Skip to content

Documentation: Grid should be an example, not a style #273

Description

@shai126

It seems to me that the styles section of the documentation is for learning about all the available utilities, and then examples shows how you can compose multiple utilities to make cool stuff.

I've now seen a couple of developers get confused when they try to figure out grids—and can't get their head around what's special about the md:w-1/3 class that makes it suitable for grids, and what other "grid utilities" are available.

I wonder whether this is a result of grid being listed in the styles section of the docs. Shouldn't grid be categorized under examples? It just composes flex, sizing and responsive utilities – it's no more a part of Tailwind than buttons or alerts are.

Or, if not, a note in the grid docs to explain that it's just comprised of whatever flex and sizing and responsive utilities you want to use.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions