Skip to main content

Environment Variables

Sprinkling css into an application is a lot like configuring the Environment Variables of your app to render correctly on the client side. Setting up the environment on the client side is also about understanding the context of fronted design that one must accept while filling the viewport with their app.

Toucaan makes it easy to conceptualize, configure, and deliver a fully realized browser environment from one place in your project.

Vendor Normalization

The first soft layer of setting up environment variables for your application is handling vendor inconsistencies up and close.

Traditionally, applications have required injecting a fairly heavy reset, reboot, or normalize css file before other application styles could be included. Toucaan does not use this strategy.

Toucaan uses the baseline method instead.

Why no normalize?

A to-do app will likely not require the block of normalization code meant for the video tag, for example. One could shed unused css programmatically at the build stage, but such a set up often leads to dead code within the project.

The Env Folder

Open the env folder inside toucaan submodule to reveal its contents:

Environment architecture

Inside the env folder you'll find two subfolders named helpers and tags each carrying a few initial defaults. Only a few baseline tags and pseudo-classes are included in the environment by default but you can add more into the context as needed.


The env must be customized according to the actual HTML vocabulary of your app.

Desktop's Case

This is how the environment for a desktop browser is reset:

Open ./toucaan/app/desktop/desktop.scss
/* Notch handling isn't required on desktops. */
/* @import '../../accessibility/notch'; */

/* ~ Other css and typeset defaults might come here */

/* Notice the first Environment Variable. */
@import '../../env/helpers/universal';

/* A baseline HTML environment. */
@import '../../env/tags/baseline/html';
@import '../../env/tags/baseline/body';
@import '../../env/tags/baseline/anchor';
@import '../../env/helpers/pseudos';

/* and so on… */

Take a look at the desktop.scss file to see a real desktop reset followed by the space for application styles to be written by you.


A desktop displays along the landscape-axis of intrinsic design, whereas a mobile on the portrait-axis.

Mobile's Case

Like with the desktop, the environment of a mobile browser can be set like so:

Open ./toucaan/app/mobile/mobile.scss
/* Read more about the notch → */
@import '../../accessibility/notch';

/* ~ Other css and type defaults here */

/* Notice the first Environment Variable. */
@import '../../env/helpers/universal';

/* A baseline HTML environment. */
@import '../../env/tags/baseline/html';
@import '../../env/tags/baseline/body';
@import '../../env/tags/baseline/anchor';
@import '../../env/helpers/pseudos';

/* and so on… */

Since most developers and designers like to work on a desktop, Toucaan recommends to configure the desktop environment first. Not mobile or mobile-first!

Head Level Configuration

A part of the configuration options provided in the _config.scss file (see the last chapter) are also environment properties.

Here are some of the things for you to configure:

  1. Decide on a color palette,
  2. Choose the right typeface(s),
  3. Host the type yourself or use a service,
  4. Apply initial defaults for common tags (or use the one provided),
  5. Choose a selection color in active and inactive states,
  6. Configure behavior and accessibility of form elements, and so on…

The key here is to break it down into small piece and config the framework as you go on to build intrinsic UX/UI for each device category that you end up supporting for your users. Contextualize properties like touch-action: auto and pointer: coarse according to the need of the medium and move them out of the way from environments that do not require those.

Go to the next chapter on Intrinsic Typography.