Container
A page wrapper. It caps the maximum width, centers horizontally, and adds side padding (max-w-*, mx-auto, px-*). It replaces the max-width + margin auto + padding repeated in every layout, and you write it with whatever semantic element you need (<main>, <section>).
Layout · TaishoDS Core, in plain HTML.
Examples
One working example per case. Each example is the HTML of its preview—copy it as is, and with Core’s CSS and JS loaded, it looks and works the same.
Centered content with max width
The container centers content and caps the reading width.
Class reference
Every value of each modifier, with its HTML ready to copy.
Size
The content’s max width (max-w-screen-*): sm, md, lg, xl…
Dashboard
Dashboard
Dashboard
Dashboard
Dashboard
Padding
Horizontal padding (px-*), from none to the largest.
Payments API
Payments API
Payments API
Payments API
Payments API
Payments API
States
The centered container (mx-auto) with its reading width.
Marketing site
Combinations
Width and padding combined.
Data pipeline
Data pipeline
Data pipeline
When to use
- Wrapping a page’s content so it doesn’t stretch edge to edge.
- You want the same width and the same side spacing on every screen.
- You need the wrapper to be a landmark (
main,section).
When not to use
- The block has to span the full width (a
banner, a full-bleed hero). - It’s how the content is laid out inside, not the page width →
stackorgrid.
Do
- One container per page region, not one inside another.
- Choose the maximum width based on what’s being read. Long-form text wants less width, not more.
Don’t
- Don’t nest containers. The padding doubles up.
- Don’t use it as a visual box. It doesn’t draw anything →
card.
TaishoDS Core
Doesn’t need JavaScript—it’s markup and CSS.
Layout: max-width and padding.
From the CDN, without a build, this component has no file of its own—it comes with taisho.base.css.
For how Core works in general, see Behavior.
Accessibility
- A layout container that adds no semantics. If it wraps a region, put it inside the matching landmark.
Verification
What was actually tested. Anything that wasn’t tested says so—we’d rather say “not verified” than claim too much.
- axe WCAG 2.2 A + AA in a real browser, in light and dark mode, before every release.
- keyboard Adds no keys of its own—it uses the browser’s native behavior.
- screen reader Not verified with a screen reader. Test it in your own combination of components, not just here, where each one appears alone and on its happy path.