How to start developing components

Important

Before you start using the City of Ghent Style Guide in your project you should read this section.

Component variables and sections

Components use context to style themselves. If no context is applied by a wrapping element it gets a base styling.

In the components/00-settings/_vars.scss file you will find a SASS map $themes that defines all section types. Atoms then base their styling on the section they are in.

How to define a new component

So you’re looking to use the City of Ghent Style Guide but find that one of the components in your design isn’t defined yet?

1. Make sure you checked everything of the checklist Can I define a new component?
2. Categorize your component following Atomic Design principles and determine whether you’re dealing with a atom, molecule or organism.
3. Start writing your code.

Checklist: Can I define a new component?

Here’s a checklist with things you need to consider before defining a new component. If you can check ALL boxes, then yaay: go ahead and create a new component.

I’ve read the CONTRIBUTING.md file in the root of the GIT repo.
The component will be used in other projects.
(if the answer is no: define a custom component in your project code base)
I’ve looked for similar looking components and couldn’t find one.
(if you did find one: define a technical variant using the method below: Share code between components)
I’ve looked for a component that serves the same purpose and couldn’t find one.
(if you did find one: define a variant in {component}.config.js)

Folder structure

ⓘ All components defined within the City of Ghent Style Guide are categorized following the atomic design principles by Brad Frost.

Component categorization

Components are always defined as one of these

• Base: Contains global configuration (ex.: colors or fonts used in theme).
• Atoms: Smallest possible components; can’t be broken down any further without ceasing to be functional.
• Molecules: Relatively simple groups of UI elements functioning together as a unit.
• Organisms: Relatively complex UI components composed of groups of Molecules and/or Atoms and/or other Organisms.
• Pages: specific instances of templates that show what a UI looks like with real representative content in place.

Component folder structure

Since the goal is to make a healthy mix between functional components and keeping our code DRY when defining components, some components will share code but still be defined as separate components.

Share code between components

Sometimes a component has a similar technical logic, but an entirely different functional meaning. For example: an alert box and a call to action (CTA) could look the same, but they’re to separate components that can be used elsewhere on the page.

When you bump into a situation like that, do this:

• Define 1 base component that:
  • contains all markup and styling.
  • is configurable.
  • is hidden in the UI.

But hey! shouldn’t variants be defined into the same component?
Good point… We’re making the distinction between functional and technical variants. Functional variants should be defined as a real/visible variant for your component. Technical variants just share code and can therefore be separate components.

• Define multiple variant components that:
  • doesn’t have its own markup and/or styling
  • include the base component with configuration

An example

Two components - alert and CTA should both be displayed as a box with a background color, title, description and (optional) button. They look the same visually, but have other functional purposes.

Folder structure:

31-molecules
├── 
│   └── CTA
│      └── cta.html.twig
│      └── cta.config.js
│   └── alert
│      └── alert.html.twig
│      └── alert.config.js
└── box.html.twig
└── box.config.js
└── _box.scss

• Box is a configurable component that can output either a CTA or alert, depending on the configuration it receives.
• Box is hidden in the UI, because it can never be used as a standalone component.

cta.html.twig

{% include '@box' with _self.context %}

cta.config.js

module.exports = {
  title: 'CTA',
  status: 'alpha',
  context: {
    title: "Call to action",
    description: "Click the button below and find out what happens.",
    href: "https://gph.to/2BpmIKC",
    link: "Click me",
    icon: "link"
  },
};