/* DARTMOOR-FUTURES.CSS 

This file is to override individual CSS IDs/classes on THIS site that for whatever reason can't be set in the cascading SCSS

The Shared National Park layouts, typography and colours set in the Gilmore GitLab files - this is the equivalent to a WordPress THEME 
WHOLE SITE SITE-SPECIFIC settings are set in _design-variables.scss and _design.scss #187129 - equivalent to CHILD THEME settings in WP.  avoid getting overwritten when a THEME change is made in GitLab and cascades through to all sites
SECTION / PAGE-SPECIFIC changes should be added here equivalent to 'Additional CSS' in WP
PAGE / INLINE STYLES are discouraged should be kept to a minimum

NB The below overrides are deliberately crass to show  what can changed.

Questions
Do we defintely know the site-specific custom files don't get overwritten when GitLabs changes occur?
Why did it take David so long to remember how to clear browser cache?
If we make a change in GitLabs (manually or via Ross making a Commit) does this get routed to the website directly via the Integration Asset or via the DXP Component Service?
*/