First composition

Search…
First composition
Let's create our first composition. With Atomic Layout a UI composition is physical and you can render it as a React component called <Composition/>. Any layout piece is a combination of its counterparts, whether it's an entire page or a small button. You can apply this principle throughout the entire application and remain consistent in the way your components are declared.
Consider the following UI element as our end goal:
Mobile design of the UI element.
Following the best practices, we are going to start from mobile design and gradually move upward bigger screens.
Creating a component
To start, let's create a new Album component that will represent our UI element.
src/components/Album.js
1
import React from 'react'
2
​
3
export const Album = () => (
4
  <p>Nothing unusual yet</p>
5
)
Copied!
Composition
Next step, let's import the Composition components from the atomic-layout package at the top of your Album file:
src/components/Album.js
1
import React from 'react'
2
import { Composition } from 'atomic-layout'
Copied!
When describing a layout composition we can split our UI element in to pieces, or areas. Looking at our design, we could have the following areas:
Although there are no strict rules regarding areas breakdown, try for area names to be meaningful in their domain. For example, favor area names like "thumbnail" or "content" over "top" or "bottom". This is especially useful when dealing with responsive layouts, as the position of an area may change. Having "top" area on the bottom right is rather ridiculous.
Composition areas are verbal representation of layout areas, sensitive to their position in space and relation to each other.
Once we are happy with the areas names, we need to write them down. We are going to create a variable areasMobile that will hold a description of our areas on mobile screens.
src/components/Album.js
1
// Template string literal helps to preserve the vertical relation
2
// of areas. Below, we've described three areas one by one,
3
// just as they appear on the design.
4
const areasMobile = `
5
  thumbnail
6
  content
7
  actions
8
`
Copied!
On its own the areasMobile variable is just a string. In order for it to be used as a blueprint for a layout composition, we need to pass it as a value to the areas prop of the Composition component:
src/components/Album.js
1
export const Album = () => (
2
  <Composition areas={areasMobile}>
3
    <p>Still nothing extraordinary</p>
4
  </Composition>
5
)
Copied!
If a Composition component accepts areas it returns React components generated based on passed areas. Those components are available in the children render function as arguments:
src/components/Album.js
1
export const Album = () => (
2
  <Composition areas={areasMobile}>
3
    /* React components based on "areasMobile" areas */
4
    {(Areas) => (
5
      <> // <- notice the React.Fragment wrapper
6
        <Areas.Thumbnail>Our thumbnail</Areas.Thumbnail>
7
        <Areas.Content>Content</Areas.Content>
8
        <Areas.Actions>Call to action</Areas.Actions>
9
      </>
10
    )}
11
  </Composition>
12
)
Copied!
Pay attention that all children (area components) are wrapped in React.Fragment (<></>). This is necessary because CSS Grid currently affects only direct children, so must make sure area components are direct children of the Composition.
Now we can render other components inside those area component to make up the desired appearance. This is an example of how this would look like:
src/components/Album.js
1
export const Album = ({ title, imageUrl, releaseYear, artistName }) => (
2
  <Composition areas={areasMobile}>
3
    {(Areas) => (
4
      <>
5
        <Areas.Thumbnail>
6
          <img src={imageUrl} alt={title} />
7
        </Areas.Thumbnail>
8
        <Areas.Content>
9
          <h3>{title}</h3>
10
          <p>{artistName} • {releaseYear}</p>
11
        </Areas.Content>
12
        <Areas.Actions>
13
          <button>Buy</button>
14
        </Areas.Actions>
15
      </>
16
    )}
17
  </Composition>
18
)
Copied!
Styling visual appearance of children UI elements, such as image or button, is not a part of this tutorial, because it's not the responsibility of Atomic Layout. Please refer to the complete example (live sandbox) at the bottom of this page for styling references.
Areas relation
Our areas template string describes a spacial relation of areas. However, to specify things like an area's dimensions, or spacing between the areas, we may use additional CSS properties.
For example, to space out the areas we can use the gap prop (that aliases grid-gap CSS property).
src/components/Album.js
1
export const Album = () => (
2
  <Composition areas={areasMobile} gap={10}>
3
    {(Areas) => (
4
      /* Same areas here... */
5
    )}
6
  </Composition>
7
)
Copied!
Prop gap={10} applies grid-gap: 10px; in the generated styles.
Read about CSS Grid to know how to describe created compositions (CSS Grid containers). You are going to use this knowledge a lot when working with the library.
Summary
In this section we have learned:
How to break down UI element to composition areas;
How to use Composition component;
How to control relation between composition areas;
Live example
Getting Started sandbox
Getting started - Previous
Installation
Next - Getting started
Responsive composition
Last modified 1yr ago
Copy link
Contents