Tailwind
Every Layout

GitHub GitHub

Installation

Install the plugin from npm:

npm install -D tailwind-every-layout@latest

Then add the plugin to your tailwind.config.js file:

import { tailwindLayouts } from 'tailwind-every-layout';

export const plugins = [
  tailwindLayouts,
];

and in your css file add your path to your config

@config '../tailwind.config.js';

Usage

Now you can use layout classes to compose layouts. Go to the Layouts page to see all the available layouts.

Composing layouts

Much like Tailwind’s utility classes, each layout utility class is designed to have a single responsibility. This means that you compose layout classes together to achive the desired overall layout.

For example, if you want to arrange elements one on top of the other and want them to be centered, you should use the stack-l class on the parent container to achieve the stacking and the center-l class for centering.

Applying layout classes

Each layout class is meant to be applied on a “container” element (non-semantic or semantic). The layout class then operates on the container itself and the child elements (usually only direct) of the container element as needed to achieve the layout.

Some layouts require one of the child elements to be specified by a class as well. For example, the Cover layout requires the cover-l class on the container element and the cover-l_center class on the child element that should be centered.

Using prop classes

Each layout class comes with sensible defaults. However, you can customize the layout by using prop classes.

For example, when you apply the stack-l class, you get the default amount of spacing between the stacked child elements. You can customize this spacing by using the stack-l-* prop classes. The class stack-l-6 will corresopond to spacing.6 in your theme (1.5rem in the Tailwind’s default theme).

Here are some things to note when using prop classes:

  • Prop classes are optional and are only required to override the layout’s defaults.
  • Prop classes require you to first apply the base layout class on the container element for them to work. This is because, to achieve their overriding behaviour, prop classes use CSS specificity by latching onto the base class.

    For instance, stack-l-6 will not work unless you also apply the stack-l class.

  • Prop classes follow the naming pattern layout_prop-value where layout is the base layout class e.g. stack-l, prop is the name of the prop e.g. space and value is the value of the prop e.g. 6.
  • All prop classes map to appropriate values in your theme.

    With the Tailwind CSS IntelliSense extension, you can conveniently see all the available prop classes for each layout class and also get autocompletion for their values.

  • You can also provide arbitrary values on the fly to any of the prop classes using Tailwind’s square bracket notation.

Plugin configuration

⚠️ Mind that these configurations are currently only adapted to work with Tailwind v4. For backwards compatibility, you can still use JS config files with Tailwind. If possible, use your CSS files for any adaptations. ️⚠️

The plugin is extensively configurable. You can configure the plugin via the layouts section of your tailwind.config.js file:

import { tailwindLayouts } from 'tailwind-every-layout';

export const theme = {
  extend: {
    layouts: ({ theme }) => ({
      // your overrides...
    }),
  },
}

export const plugins = [
  tailwindLayouts,
  // ...
];

See the default theme for all available theme options.

Some options which are not so theme related are configured by passing an object as an argument while registering the plugin:

import {
  tailwindLayouts,
  defaultOptions }
from 'tailwind-every-layout';

export const theme = {
  // ...
}

export const plugins = [
  tailwindLayouts({
    ...defaultOptions,
    // your overrides...
  }),
  // ...
];

See the default options for all available plugin options.

Let’s look at some available configuration options.

Using a global measure

The measure is the width of a line of text. Choosing a good measure is important for readability.

A default measure value of 65ch is used by all the layouts that need a measure. This value can be configured via the measure option in the layouts section of your tailwind.config.js file.

export const theme = {
  extend: {
    layouts: ({ theme }) => ({
      measure: '75ch',
      // ...
    }),
  },
}

The plugin also sets this measure value globally with some default exceptions:

* {
  max-width: 65ch;
}

html,
body,
div,
header,
nav,
main,
footer {
  max-width: none;
}

You can specify the exceptions via the measureExceptions plugin option. For example, to exclude <section> elements:

export const plugins = [
  tailwindLayouts({
    ...defaultOptions,
    measureExceptions: [
      ddefaultOptions.measureExceptions,
      'section',
    ].join(','),
  }),
];

If you want to completely opt out of the global measure, you can set the useGlobalMeasure option to false:

export const plugins = [
  tailwindLayouts({
    ...defaultOptions,
    useGlobalMeasure: false,
  }),
];

Using with Tailwind Typography

The Tailwind Typography plugin also sets a measure (maximum width) for the prose container. The value is 65ch which is also the default value used by this plugin. If you have overridden the default value with a custom value, you sould probably use the same for prose content as well.

You can do this by applying max-w-measure / max-is-measure along with the prose class to the prose container.

<div class="prose max-w-measure">
  <!-- prose content -->
</div>

As the layout of children of the prose container is controlled by the typography plugin, you can exclude them too. In your tailwind.config.js file:

export const plugins = [
  tailwindLayouts({
    ...defaultOptions,
    measureExceptions: [
      defaultOptions.measureExceptions,
      '.prose *:not(img):not(video)',
    ].join(','),
  }),
];

By doing this we effectively set max-width: none to all children of a prose container, except we do not want to override max-width:100% set by Preflight for <img> and <video> elements.

Overriding measure for an element

If for some reason you want to override the measure for a specific element, you can always use the max-w-none / max-is-none class.

Using scrollbar styles

Layouts like the Reel use a scrollbar to indicate scrollable content. The plugin allows you to style scrollbars in two ways:

Global scrollbar styles

You can set a global style for your scrollbars by setting the useGlobalScrollbarStyles option to true:

export const plugins = [
  tailwindLayouts({
    ...defaultOptions,
    useGlobalScrollbarStyles: true,
  }),
];

The scrollbar theme itself can be configured in the layouts section of your tailwind.config.js file:

export const theme = {
  extend: {
    layouts: ({ theme }) => ({
      scrollbarThumbColor: theme('colors.gray.500'),
      scrollbarTrackColor: theme('colors.gray.200'),
      scrollbarSize: 'medium', // 'thin' | 'medium' | 'thick'
      scrollbarBorderRadius: '9999px', // 9999px | 0px
    }),
  },
}

Tip: Use CSS properties for different colors in light and dark mode. For example, in your global.css file:

@import 'tailwindcss';

/* ... */

@layer base {
  :root {
    --tw-scrollbar-track: var(--color-gray-50);
    --tw-scrollbar-thumb: var(--color-gray-400);
    --tw-scrollbar-invert-track: var(--color-gray-900);
    --tw-scrollbar-invert-thumb: var(--color-gray-500);
  }
  .dark {
    --tw-scrollbar-track: var(--tw-scrollbar-invert-track);
    --tw-scrollbar-thumb: var(--tw-scrollbar-invert-thumb);
  }
}

If you do not have access to a global.css file, the same can be achieved via the addBase() Plugin API in your tailwind.config.js file.

Then in the layouts section of your tailwind.config.js file:

export const theme = {
  extend: {
    layouts: ({ theme }) => ({
      // 🌗 Color scheme aware CSS properties!
      scrollbarThumbColor: 'var(--tw-scrollbar-thumb)',
      scrollbarTrackColor: 'var(--tw-scrollbar-track)',
    }),
  },
}

Element-specific scrollbar styles

You can also apply scrollbar styles to specific elements. Use the scrollbar utility for this purpose.

Setting a base spacing

The plugin uses a base spacing value of 1rem for all the layouts that need a spacing between or around elements. This value can be configured via the baseSpacing option in the layouts section of your tailwind.config.js file.

export const theme = {
  extend: {
    layouts: ({ theme }) => ({
      baseSpacing: '1.5rem',
    }),
  },
}

Using CSS logical properties

CSS logical properties have good support across all modern browsers. They are a great way to write CSS that adapts to the reading direction of the document. You can use logical properties in your layouts by setting the useLogicalProperties option to true:

export const plugins = [
  tailwindLayouts({
    ...defaultOptions,
    useLogicalProperties: true,
  }),
];

If you want to use min/max width and height utility classes with logical properties, you have to replace the traditional w (width) and h (height) prefixes with is (inline size) and bs (block size). For example:

// Width / Inline Size
<p class="center-l_max-w-xs">Physical Properties</p>
<p class="center-l_max-is-xs">Logical Properties</p>

// Height / Block Size
<p class="center-l_max-h-xs">Physical Properties</p>
<p class="center-l_max-bs-xs">Logical Properties</p>

Using custom class names

You can override the default class names for some or all layouts using the classNames option:

export const plugins = [
  tailwindLayouts({
    ...defaultOptions,
    classNames: {
      ...defaultOptions.classNames,
      stack: 'my-stack',
    }
  }),
];

Note that once you change the base layout class name, its prop class names will also change accordingly: stack-l-6 will now be my-stack-6.