mirror of
https://github.com/apache/superset.git
synced 2026-05-22 08:15:36 +00:00
Snapshots all four versioned Docusaurus sections at v6.1.0, cut from master after the version-cutting tooling (#39837), broken-internal- links fix (#40102), and user_docs rename (#40171) all landed. With the rename in place, all four sections now produce parallel-named files at the docs/ root (no more bare `versioned_docs/` outlier). Versioning behavior: lastVersion stays at current for every section, so the canonical URLs (/user-docs/..., /admin-docs/..., /developer-docs/..., /components/...) continue to render content from master. The current version is consistently labeled "Next" with an unreleased banner, and 6.1.0 is a historical pin accessible only via its explicit version segment. Component playground: previously disabled: true in versions-config.json, now enabled and versioned. Snapshot includes: - All MDX content for the four sections. - Auto-gen captured fresh: 74 database pages (engine spec metadata), ~1,800 API reference files (openapi.json), 59 component pages (Storybook stories). - Data imports frozen at cut time into snapshot-local _versioned_data/ dirs: user_docs_versioned_docs/version-6.1.0/_versioned_data/src/data/databases.json (canonical 80-database diagnostics from master, preserved by the generator's input-hash cache) admin_docs_versioned_docs/version-6.1.0/_versioned_data/data/countries.json admin_docs_versioned_docs/version-6.1.0/_versioned_data/static/feature-flags.json developer_docs_versioned_docs/version-6.1.0/_versioned_data/static/data/components.json - Import paths in deeply-nested files rewritten so they still resolve from one directory deeper inside the snapshot. - developer_docs/extensions/overview.md snapshot has the FIXED ./mcp.md form (from #40102), so the SPA-nav 404 isn't baked into the 6.1.0 version. Verified via full yarn build: exit 0, no broken links surfaced by onBrokenLinks: throw.
3.5 KiB
3.5 KiB
title: Grid sidebar_position: 1
Grid Component
The Grid component provides a flexible layout system for arranging content in rows and columns.
Props
| Prop | Type | Default | Description |
|---|---|---|---|
gutter |
number or [number, number] |
0 |
Grid spacing between items, can be a single number or [horizontal, vertical] |
columns |
number |
12 |
Number of columns in the grid |
justify |
string |
'start' |
Horizontal alignment: 'start', 'center', 'end', 'space-between', 'space-around' |
align |
string |
'top' |
Vertical alignment: 'top', 'middle', 'bottom' |
wrap |
boolean |
true |
Whether to wrap items when they overflow |
Row Props
| Prop | Type | Default | Description |
|---|---|---|---|
gutter |
number or [number, number] |
0 |
Spacing between items in the row |
justify |
string |
'start' |
Horizontal alignment for this row |
align |
string |
'top' |
Vertical alignment for this row |
Col Props
| Prop | Type | Default | Description |
|---|---|---|---|
span |
number |
- | Number of columns the grid item spans |
offset |
number |
0 |
Number of columns the grid item is offset |
xs, sm, md, lg, xl |
number or object |
- | Responsive props for different screen sizes |
Examples
Basic Grid
import { Grid, Row, Col } from '@superset-ui/core';
function Example() {
return (
<Grid>
<Row gutter={16}>
<Col span={8}>
<div>Column 1</div>
</Col>
<Col span={8}>
<div>Column 2</div>
</Col>
<Col span={8}>
<div>Column 3</div>
</Col>
</Row>
</Grid>
);
}
Responsive Grid
import { Grid, Row, Col } from '@superset-ui/core';
function Example() {
return (
<Grid>
<Row gutter={[16, 24]}>
<Col xs={24} sm={12} md={8} lg={6}>
<div>Responsive Column 1</div>
</Col>
<Col xs={24} sm={12} md={8} lg={6}>
<div>Responsive Column 2</div>
</Col>
<Col xs={24} sm={12} md={8} lg={6}>
<div>Responsive Column 3</div>
</Col>
<Col xs={24} sm={12} md={8} lg={6}>
<div>Responsive Column 4</div>
</Col>
</Row>
</Grid>
);
}
Best Practices
- Use the Grid system for complex layouts that need to be responsive
- Specify column widths for different screen sizes to ensure proper responsive behavior
- Use gutters to create appropriate spacing between grid items
- Keep the grid structure consistent throughout your application
- Consider using the grid system for dashboard layouts to ensure consistent spacing and alignment