Instructions
1. Start here
Veya has four homepages (Home, Home Daylight, Home Full-bleed, Home Travel), each also in dark mode (Home Dark, Home Daylight Dark, Home Full Bleed Dark, Home Travel Dark: the same page with theme-dark on its Body), the listing pages for journeys, places, days out and offers, the planning and booking pages, and a page for each journey, destination, day out and post. Keep the homepage you like as the Home page in Page settings and delete or unpublish the rest.
Every page shares one header (Navbar), one phone menu (Phone Menu) and one footer (Footer): edit them once, in the component, and every page follows.
Every button that opens a page is one component, Button. Select one and set its Variant (Primary, Outline, Ink or Link, each in Small, regular or Large, and On Dark), its Label and its Link; to restyle every button at once, edit the component. The buttons of a form or a part are their own elements, because a form sends with its own button and an interaction needs its own trigger: Search, Send, Filters, Sort, Clear the filters, and the Continue, Back and Change steps on the Book page. They take the same colours, type and corners from the variables.
The two versions of Days out and of Offers share four blocks, each one component: Special Dates and Make A Week (Days out, by the hour and by host), Last Few Places and Group Prices (Offers, with coupons). Double-click one to edit it and both pages follow.
Home Dark, Home Daylight Dark, Home Full Bleed Dark and Home Travel Dark are copies of their homepage with theme-dark on the Body, there to show the night. Edit the homepage you keep; to make it dark, give its Body theme-dark rather than keeping both, and delete the copies you don't use.
2. Journeys, places, days out and posts
Each lives in the CMS (Journeys, Destinations, Day Experiences, Posts, Guides), with Itineraries, Stays and Dates holding a journey's day by day, its stays and its departures. Add an item and it appears on its listing page and on the homes' rows by itself.
Each journey, destination and day out has a Page design field: three layouts per family, chosen per item (a journey: Column, Stack or Route; a destination: Atlas, Halves or Postcards; a day out: Column, Route or Story). A post's Related layout chooses one, two or three related journeys. In a post's or a day out's text, put who said a quote in Heading 3 straight after it: it becomes the card under the quote.
The designed blocks — the region blocks, the mosaic, the month pages, the departure boards, the timetables, the seasons — are edited in the Designer, each row or card its own element.
Links from a static section to a journey, destination or day out are typed addresses (/journey/its-slug). If you change an item’s slug in the CMS, change those links too, or set them to the item’s page in Link settings. A few things are written twice on purpose: the stops of Home Daylight’s week (under the drawing, which scrolls sideways on phones, and in the list shown on phones), the featured offer on Offers (also in the offers grid), a place on Destinations by month (in each month it is good), and the Book page, drawn out for each journey as a demonstration to connect to your booking system (see section 5).
3. Colour, type and space
Every colour is a variable. The Colour collection names each colour by its job (Page, Surface, Text, Text Muted, Border, Accent, Deep, Pale, Glow…); the Palette collection holds the raw values, with a Night mode. Change a colour in Palette and every page follows, by day and by night.
A coloured block (deep pine, sunlight, sage, cream, the frosted plate over a photograph) wears a Colour mode on its class, so the words on it take that ground's colours without a class of their own. The Style Guide shows each.
Type sizes, line heights, weights and letter spacing are the Type collection; spacing, sizes and radii are Space & shape. Archivo is the only typeface.
4. Tabs, choosers, filters and menus
Every interactive part works by Webflow Interactions, site-wide, with no code. A part's root carries data-part, each of its buttons data-option (a number) and each panel data-i (the number of the button that shows it). Pressing a button gives it the is-on combo class and shows its panels, hiding the others; is-hidden is the combo that hides a panel.
Some parts take turns by themselves: the guides’ reviews on Home, the hero and the countries on Home Full Bleed, the Halves design of a destination and the Deck design of a journey. The canvas shows the first turn; the others are hidden layers, each with its own words and photograph. To edit one, select it in the Navigator and click the eye beside it: it shows on the canvas until you click the eye again, and the published site is unchanged. A tab names its turn with data-turn-to (a number) and a next or previous button with data-turn-step; the GSAP script does the turning.
Two parts on Home are laid out by the GSAP script and look plainer on the canvas. The seasons show as four rows, each season’s words followed by its photograph; the script pins them into one screen and turns the year as visitors scroll. To add a season, duplicate a season’s words and its photograph together, keep each pair in that order, and add its name to the list of seasons above them. The strip of places beside the guides is one list that the script loops: the canvas shows the first few, and the rest are in the Navigator.
- To change how a pressed button or an open panel looks, select it and style its is-on (or is-hidden) combo class.
- To add a tab or a chip, duplicate the last button and its panel and give both the next number. The interactions already cover up to 7 options for most parts; one more needs one more interaction: duplicate the last one in the Interactions panel and change the numbers. The Destination chips on the journeys and days-out pages are the exception: they come from the Destinations collection and link to each destination's page, so add, rename or delete a destination in the CMS and its chip follows, with no interaction to add. The other chips on those two pages filter the cards. Each has one interaction, named like "Journey cards follow the style chip hiking", that hides the cards whose card-keywords don't match it (an is-out- class). A new chip needs its own: duplicate one, change the word in its target, and give it the next is-out- class.
- Keep the is-on, is-off, is-hidden, is-chosen and is-reached combo classes and the is-out- classes: interactions add them as the page is used. A hidden block at the end of the Style Guide (style-guide_states in the Navigator) wears each of them once, so Clean up keeps them. Don't delete it; a new state gets one Div there with the same classes.
5. Forms, search and booking
Contact, Plan a trip, Tell us in one sentence, Book a trip and the Newsletter are native Webflow forms, each named, with its success and error messages: submissions arrive in Site settings → Forms. The selects inside them are native Select fields; edit their options in the Select's settings.
The trip search (on the four homepages and their dark copies, Journeys and Days out: 12 forms) is three native Select fields, Where, When and Who (What on a day-out search), and a Search button. A visitor picks one choice in each and stays on the page; Search then opens the Journeys page or the Days out page with the choices in the address, for example /tours?where=Italy&when=June&who=4. The quick plan sends its words to the plan page.
Search does not filter the results by itself. Webflow can't read the address, so without code the Journeys or Days out page opens with every journey or day out, whatever was chosen, and the visitor narrows it with the chips. To open the page already narrowed to the choices, add the optional script below.
To change a search's choices, select its Where, When or Who field and edit the options in the Select's settings: the text is what visitors see, the value is what the search sends. The Where options are typed, not drawn from the CMS: when you add or rename a destination, do the same in each search's Where field.
On those two pages every chip filters the cards and Sort by sorts them, with no code: each sort order is its own Collection List (data-sort-list, the option's number), and the Destination chips open the destination's page. To send the search to your own booking system instead, set the form's Action in its Form settings to that system's search address and give each Select the name it expects. To open the page already narrowed to the search's choices, keep them in the fields, count the cards and let two chips in one group widen the list, add the optional script below.
Paste it into the Journeys page and the Days out page: Page settings → Custom code → Before </body> tag. Custom code runs on a paid Site plan, on the published site. The script reads the chips, the first sorted list and each card's card-keywords element, whose data- attributes are bound to CMS fields (data-region, data-styles, data-months, data-difficulty, data-days, data-price on a journey; data-country, data-kind, data-place, data-hours, data-when on a day out). Nothing in it names a place or a style, so a destination, style or journey you add, rename or delete needs no change to it.
<script>
/* Veya: live search and filters (optional custom code, added after purchase).
Paste in Page settings → Custom code → Before </body> tag, on the Journeys page (/tours)
and on the Days out page (/experiences). Custom code runs on a paid Site plan.
It reads everything from the page itself: the words in the address bar, the filter chips
and the cards your CMS publishes. Add, rename or delete a destination, a style or a
journey, publish, and it follows: nothing here names a place, a style or a price.
The template filters and sorts without it; with it, chips in one group widen the list
(Hiking or Coast), Destination chips filter in place instead of opening the destination,
the chips show counts, the heading counts the cards, and the search's choices stay. */
(function () {
var results = document.querySelector('[data-part$="-results"]');
if (!results) return;
/* The cards: one list per sort order (data-sort-list), the same cards in each. The first list is
read; every copy of a card shows or hides with it. */
var lists = [].slice.call(results.querySelectorAll('[data-sort-list]'));
var all = [].slice.call(results.querySelectorAll('.w-dyn-item')).filter(function (item) {
return !item.closest('[data-part="filter-group"]'); // a chip made by the CMS is an item too
});
var cards = lists.length ? [].slice.call(lists[0].querySelectorAll('.w-dyn-item')) : all;
if (!cards.length) return;
function key(item) { var a = item.querySelector('a[href]'); return a ? a.getAttribute('href') : item.textContent; }
/* The template hides cards with is-out-… classes; from here on this script decides. */
var css = document.createElement('style');
css.textContent = '.w-dyn-item[class*="is-out-"]{display:block}';
document.head.appendChild(css);
var groups = [].slice.call(results.querySelectorAll('[data-part="filter-group"]'));
var MONTHS = ['january', 'february', 'march', 'april', 'may', 'june', 'july', 'august', 'september', 'october', 'november', 'december'];
var DAYS = ['monday', 'tuesday', 'wednesday', 'thursday', 'friday', 'saturday', 'sunday'];
var STOP = ['any', 'anywhere', 'with', 'and', 'the', 'for', 'from', 'day', 'days', 'month', 'months', 'traveller', 'travellers', 'people', 'person'];
function norm(s) {
return (s || '').toString().normalize('NFD').replace(/[̀-ͯ]/g, '').toLowerCase()
.replace(/&/g, ' and ').replace(/[^a-z0-9€]+/g, ' ').trim();
}
function words(s) { return norm(s).split(' ').filter(function (w) { return w.length > 2 && STOP.indexOf(w) < 0; }); }
function amount(s) { return parseFloat(String(s).replace(/[^\d.]/g, '')); }
function full(w) { // "jan" → "january", "tue" → "tuesday"
var all = MONTHS.concat(DAYS);
for (var i = 0; i < all.length; i++) if (w.length >= 3 && all[i].indexOf(w) === 0) return all[i];
return w;
}
/* What each card says: all its words (a hidden Text Block bound to CMS fields counts too),
its length in days or hours, its price and its group size. */
function textOf(el) { // every piece of text, spaced, so "7" + "days" + "Dolomites" stay apart
var out = [], walk = document.createTreeWalker(el, NodeFilter.SHOW_TEXT);
while (walk.nextNode()) out.push(walk.currentNode.nodeValue);
return out.join(' ');
}
function spread(t) { // "May to October" → every month between; "weekends" → saturday sunday
var n = ' ' + norm(t) + ' ';
n = n.replace(/ (january|february|march|april|may|june|july|august|september|october|november|december) to (january|february|march|april|may|june|july|august|september|october|november|december) /g, function (m, a, b) {
var i = MONTHS.indexOf(a), out = [];
for (var k = 0; k < 12; k++) { out.push(MONTHS[(i + k) % 12]); if (MONTHS[(i + k) % 12] === b) break; }
return ' ' + out.join(' ') + ' ';
});
return n.replace(/ weekends? /g, ' saturday sunday ').replace(/ weekdays /g, ' monday tuesday wednesday thursday friday ');
}
/* A card's hidden keywords: an element marked data-keywords whose other data- attributes are bound
to CMS fields, read as "name value" (data-difficulty="3" → "difficulty 3"). */
function keywordsOf(card) {
var out = [];
[].forEach.call(card.querySelectorAll('[data-keywords]'), function (el) {
[].forEach.call(el.attributes, function (a) {
if (a.name.indexOf('data-') === 0 && a.name !== 'data-keywords') out.push(a.name.slice(5).replace(/-/g, ' ') + ' ' + a.value);
});
});
return out.join(' ');
}
var info = cards.map(function (card, i) {
var text = (textOf(card) + ' ' + keywordsOf(card)).replace(/(\d),(\d{3})/g, '$1$2');
var len = text.match(/(\d+)\s*(days?|hours?)\b/i);
var price = text.match(/€\s?(\d[\d.]*)/);
var max = text.match(/max\.?\s*(\d+)/i);
var copies = all.filter(function (item) { return key(item) === key(card); });
return { card: card, copies: copies.length ? copies : [card], order: i, text: spread(text) + ' ', length: len ? +len[1] : null, price: price ? amount(price[1]) : null, max: max ? +max[1] : null };
});
/* A chip's words without its count: "Italy 2" → "Italy". */
function label(chip) {
var c = chip.cloneNode(true);
[].forEach.call(c.querySelectorAll('*'), function (e) { if (/^\s*\d+\s*$/.test(e.textContent)) e.remove(); });
return c.textContent.replace(/\s+/g, ' ').trim();
}
/* How a chip decides whether a card fits, read from its own words. */
function rule(chip) {
var l = label(chip);
if (/€/.test(l) && /up to/i.test(l)) { var cap = amount(l.match(/€\s?([\d.,]+)/)[1].replace(/,/g, '')); return function (c) { return c.price != null && c.price <= cap; }; }
if (/\d/.test(l) && /(day|hour)/i.test(l)) {
var n = (l.match(/\d+/g) || []).map(Number), lo = /up to/i.test(l) ? 0 : Math.min.apply(null, n), hi = Math.max.apply(null, n);
return function (c) { return c.length != null && c.length >= lo && c.length <= hi; };
}
if (/\d/.test(l)) { // "1–2 · easy" under "Difficulty": the card says "difficulty 3"
var group = chip.closest('[data-part="filter-group"]');
var title = group && (document.getElementById(group.getAttribute('aria-labelledby') || '') || group.firstElementChild);
var unit = title ? norm(title.textContent).split(' ')[0] : '';
var m = (l.match(/\d+/g) || []).map(Number), low = Math.min.apply(null, m), high = Math.max.apply(null, m);
var find = new RegExp(' ' + unit + ' (\\d+) ');
return function (c) { var f = unit && c.text.match(find); return !!f && +f[1] >= low && +f[1] <= high; };
}
var keys = [norm(l)], v = chip.getAttribute('data-value');
if (v && !/^\d+$/.test(v)) keys.push(norm(v));
keys = keys.concat(keys.map(full)).filter(Boolean);
var day = keys.some(function (k) { return DAYS.indexOf(k) >= 0; });
var month = keys.some(function (k) { return MONTHS.indexOf(k) >= 0; });
return function (c) {
if (day && / (daily|every day) /.test(c.text)) return true;
if (month && / (all year|year round) /.test(c.text)) return true;
return keys.some(function (k) { return c.text.indexOf(' ' + k) >= 0; });
};
}
var chips = [];
groups.forEach(function (g, gi) {
[].forEach.call(g.querySelectorAll('[data-chip]'), function (chip) {
chips.push({ el: chip, group: gi, fits: rule(chip), count: [].filter.call(chip.querySelectorAll('*'), function (e) { return /^\s*\d+\s*$/.test(e.textContent); })[0] });
});
});
/* A group filters only when the cards hold its kind of fact for every option it offers
(an option whose count reads 0 aside). A group whose facts are not on the cards yet
(say, months) is left alone, so it never empties the list by mistake. */
/* Cards with a hidden keywords block (data-keywords) declare their facts: then a group filters as
soon as any of its options can be answered, and an option nothing matches shows 0. */
var declared = cards.some(function (card) { return card.querySelector('[data-keywords]'); });
var usable = {};
groups.forEach(function (g, gi) {
var mine = chips.filter(function (ch) { return ch.group === gi && !(ch.count && +ch.count.textContent.trim() === 0); });
var answered = mine.filter(function (ch) { return info.some(ch.fits); }).length;
if (mine.length && (declared ? answered > 0 : answered === mine.length)) usable[gi] = true;
});
/* Counts: a chip that shows one (or asks for one with data-chip-count) shows how many cards fit it. */
var countClass = (chips.filter(function (ch) { return ch.count; })[0] || {}).count;
countClass = countClass ? countClass.className : '';
chips.forEach(function (ch) {
if (!usable[ch.group]) return;
if (!ch.count && ch.el.hasAttribute('data-chip-count')) {
ch.count = document.createElement('span');
ch.count.className = countClass;
ch.el.appendChild(ch.count);
}
if (ch.count) ch.count.textContent = info.filter(ch.fits).length;
});
function pressed(el) { return el.classList.contains('is-on') || el.getAttribute('aria-pressed') === 'true'; }
var text = { terms: [], max: null }; // each typed term must match; any of its words will do
/* The heading that says "7 journeys" or "7 days out": its number is the element marked data-count.
The template swaps it for "Matching journeys" (data-heading="some") once a chip is pressed;
with this script the count stays. */
var count = results.querySelector('[data-count]') || results.querySelector('[data-heading="all"] > span') || results.querySelector('[aria-live] > span');
var nounEl = count && count.nextElementSibling;
var noun = nounEl ? nounEl.textContent.trim() : '';
function apply() {
var on = chips.filter(function (ch) { return usable[ch.group] && pressed(ch.el); });
var shown = 0;
info.forEach(function (c) {
var fits = Object.keys(usable).every(function (g) {
var mine = on.filter(function (ch) { return ch.group == g; });
return !mine.length || mine.some(function (ch) { return ch.fits(c); });
});
if (fits && text.terms.length) fits = text.terms.every(function (term) { return term.some(function (w) { return c.text.indexOf(' ' + w) >= 0; }); });
if (fits && text.max && c.max != null) fits = c.max >= text.max;
c.copies.forEach(function (copy) { copy.style.display = fits ? '' : 'none'; });
if (fits) shown++;
});
[].forEach.call(results.querySelectorAll('[data-heading]'), function (h) { h.classList.toggle('is-hidden', h.getAttribute('data-heading') !== 'all'); });
if (count) count.textContent = shown;
if (nounEl) nounEl.textContent = shown === 1 ? noun.replace(/^(\S+?)s\b/, '$1') : noun;
}
/* After the template's own interaction has run, make sure the chip ended as it should: a chip
you add (or a CMS-made one) works with no interaction of its own, and a one-choice group
(length, month, budget…) lets go of its chip on a second click, as on the React site. */
function remember(e) {
var chip = e.target.closest && e.target.closest('[data-chip]');
if (chip && (e.type === 'pointerdown' || e.key === 'Enter' || e.key === ' ')) chip.veyaWasOn = pressed(chip);
}
results.addEventListener('pointerdown', remember, true);
results.addEventListener('keydown', remember, true);
function settle(chip) {
/* no pointer (a keyboard or a script): a chip with an interaction (data-mode) has already turned over */
var was = typeof chip.veyaWasOn === 'boolean' ? chip.veyaWasOn : chip.hasAttribute('data-mode') ? !pressed(chip) : pressed(chip);
delete chip.veyaWasOn;
var single = chip.getAttribute('data-mode') === 'choose';
if (single && !was) [].forEach.call(chip.closest('[data-part="filter-group"]').querySelectorAll('[data-chip]'), function (other) {
if (other !== chip) other.classList.remove('is-on');
});
chip.classList.toggle('is-on', !was);
}
/* Sorting is the template's own (one list per order). A Destination chip is a link to the
destination's page; here it filters in place instead. */
results.addEventListener('click', function (e) {
var hit = e.target.closest('[data-chip]');
if (hit && hit.tagName === 'A') e.preventDefault();
if (hit) setTimeout(function () { settle(hit); apply(); }, 120);
if (e.target.closest('[data-clear]')) setTimeout(function () {
chips.forEach(function (ch) { ch.el.classList.remove('is-on'); });
text.terms = []; text.max = null; apply();
}, 80);
});
/* What the visitor chose in the search: keep it in the fields, press the chips it names, and
search the cards for the rest. */
function fromAddress() {
var params = new URLSearchParams(location.search);
[].forEach.call(document.querySelectorAll('form[data-part="trip-search"] select[name], form[data-part="trip-search"] input[name]:not([type="hidden"])'), function (field) {
var v = params.get(field.name);
if (!v || field.name.indexOf('cf-') === 0) return;
if (field.tagName === 'SELECT' && ![].some.call(field.options, function (o) { return o.value === v; })) return;
field.value = v;
});
['where', 'when', 'what'].forEach(function (key) {
var term = norm(params.get(key));
if (!term) return;
var hit = chips.filter(function (ch) {
if (!usable[ch.group]) return false;
var l = norm(label(ch.el)), v = norm(ch.el.getAttribute('data-value'));
return l === term || v === term || full(l) === full(term) || (term.length >= 3 && (l.indexOf(term) === 0 || term.indexOf(l) === 0));
})[0];
if (hit) { if (!pressed(hit.el)) { hit.el.veyaWasOn = false; hit.el.click(); } return; }
var w = words(term).map(full);
if (w.length && info.some(function (c) { return w.some(function (x) { return c.text.indexOf(' ' + x) >= 0; }); })) text.terms.push(w);
});
var who = parseInt(params.get('who'), 10);
if (who > 0) text.max = who;
if (params.has('cf-turnstile-response')) {
params.delete('cf-turnstile-response');
history.replaceState(null, '', location.pathname + (params.toString() ? '?' + params : '') + location.hash);
}
setTimeout(apply, 120);
}
if (document.readyState === 'complete') setTimeout(fromAddress, 300);
else window.addEventListener('load', function () { setTimeout(fromAddress, 300); });
})();
</script>6. How to edit GSAP animations
The arrivals (things rising into place, photographs unveiling, a chart's bars growing, the mega menu's items) are Interactions named "Arrival: …" in the Interactions panel: change their timing there.
Everything else that moves is one GSAP script in Site settings → Custom code → Footer code. It uses ScrollTrigger, Observer and ScrollTo: keep the three on in Site settings → GSAP. Each motion finds its elements by a custom attribute (Element settings → Custom attributes). Nothing moves for a visitor who asks for reduced motion.
Element map: the attribute, then what moves.
- [data-seasons] (with data-stage, data-seasons-words, data-seasons-photos, data-seasons-grounds, data-seasons-rail): Home's pinned "Where to go" screen turns the year season by season as it is scrolled.
- [data-carousel-track] and [data-carousel-arrow="prev" | "next"]: a row of cards; each arrow glides it by one card.
- [data-edge][data-swell]: a wave that rises from flat as its block comes up the screen.
- [data-edge][data-flow]: a wave that keeps travelling while it is on screen.
- [data-turn] (with data-turn-item, data-turn-to, data-turn-step, data-turn-hold): a section that takes turns by itself, a hero's places or a country's reasons.
- [data-marquee] and [data-pause]: the marquee's belt crossing the frame; the pause button stops it.
- [data-split-flap] and [data-flap]: a departure board's letters rolling into place.
- [data-drawline] (with data-draw-line, data-draw-rider): a ticket's route drawing itself, the sun riding from the first stop to the last.
- [data-stack] (with data-stack-photo, data-stack-rise): a stack of cards settling as it is scrolled.
- [data-depth-scope] and [data-depth]: a drawing's layers leaning with the pointer. [data-drift]: a layer sliding against the scroll.
- [data-still-only]: shown only to visitors who ask for reduced motion.
Change the timing: the numbers at the top of the script, in seconds (pixels for rise). Save, then publish.
const TIMING = { enter: 0.7, draw: 0.8, loop: 28, flow: 4, quiet: 0.16, reveal: 20, stuck: 8, wheel: 0.8, glide: 0.5, follow: 0.8, scrub: 0.6, zoom: 1.14, rise: 40 };
const EASE = { enter: "expo.out", quiet: "power1.inOut", exit: "power3.in", glide: "power3.out" };Add a delay or change an ease on one tween:
gsap.to(el, { y: 0, duration: TIMING.enter, delay: 0.2, ease: EASE.enter });Change where a ScrollTrigger starts: a line draws when its top reaches 85% of the screen. Write "top 70%" to start it later.
scrollTrigger: { trigger: frame, start: "top 85%" }Remove the motion, step by step:
- 1. Open Site settings → Custom code → Footer code.
- 2. To pause it while you try the site without it, put /* on the line after <script> and */ on the line before </script>. To remove it, delete the <script> and everything in it. Each motion's block starts with a /* ── … */ comment, so you can also delete one block alone; its ScrollTriggers go with it.
- 3. Save changes, then publish.
- 4. What changes: the pinned "Where to go" screen stays on its first season, the bar stays where it is and never floats or steps away, the mouse wheel scrolls in steps, the carousel arrows stop moving the rows (a swipe still scrolls them), the waves stay still, sections show their first turn, the marquee and the departure board stand still. Every page still reads and works. Turn off the three GSAP plugins in Site settings → GSAP if nothing else uses them.
7. Drawings and icons
The landscapes, waves, postmarks and icons are SVG in Code Embeds, drawn to take their colour from the text colour around them: change the colour of the element that holds them, not the SVG. Their words (a postmark's place and year) are in the embed's code.
8. Night
Night is a class, not a switch: give a page's Body the class theme-dark and the whole page turns to night; give it to a Div Block around a section and only that band does. It switches the Palette to its Night mode and applies the Colour and Scene collections under it. Put it on the Body or on a wrapper of its own, because a second class on an element becomes a combo class. Edit the night's colours in the Palette collection's Night mode; the Style Guide shows them on a dark panel.

