import * as React from 'react';
import DocPage from '../components/DocPage/DocPage';
import GuidesNavigationFooter from '../components/GuidesNavigationFooter';
import { link, code } from '../utils/helpers';
import { CodeSnippet } from '@fluentui/docs-components';
import { Header } from '@fluentui/react-northstar';
const Category = props =>
{props.content}
; export default () => ({code('Flex')}, {code('Grid')} and {code('Layout')} components handle layout aspects. The {code('Flex')}{' '} component is for laying out items in one direction, while the {code('Grid')} component is made for two dimensional layouts. Visit the {link('Layout guide', '/layout')} page for a detailed comparison between{' '} {code('Flex')} and {code('Grid')}.
The {code('Layout')} component is now deprecated. Its purpose was arrangement of the content of a component.{' '} {code('Flex')} or {code('Grid')} component should be used instead of the {code('Layout')} component.
{code('Box')} is a utility component that is often used by Fluent UI to implement higher-level components. By default, it renders styled {code('div')} element.
The cases when client might want to use it are very exceptional, and all are about applying custom styles to rendered {code('div')} element. However, more robust approach that won't break theming consistency is to instead create a custom component and define related styles as part of a theme. Visit{' '} {link('Integrate Custom Components', '/integrate-custom-components')} page to see how this can be done.
{link('Segment', '/components/segment')} groups related content together. It shouldn't be used to handle layout aspects.
} />As each theme is reqular JS object you can reassign properties: