Nightshade’s visual identity rests on six custom color tokens compiled intoDocumentation Index
Fetch the complete documentation index at: https://mintlify.com/apursley2012/nightshade/llms.txt
Use this file to discover all available pages before exploring further.
assets/main.css via Tailwind CSS. Each token carries a deliberate role — from the void-black canvas to the amber candleflame that marks your active position in the navigation. Understanding these tokens is the first step to reading or modifying the UI’s dark-witch aesthetic.
Color Tokens
The six tokens are registered as Tailwind theme extensions and resolve to the following hex values.| Token | Hex | Usage |
|---|---|---|
witch-dark | #0b0d10 | Page background, card backgrounds, nav background |
witch-plum | #581c87 | Borders, inactive nav, SmokeLayer blob, decorative elements |
witch-turquoise | #14b8a6 | Primary interactive color, active states, scrollbar thumb |
witch-amber | #f59e0b | Active nav flame, hover highlights, candle flame, headings |
witch-moonlight | #e2e8f0 | Default text color, subtle UI elements |
witch-teal | #0d9488 | Secondary accent, SmokeLayer blob, text glow |
bg-witch-dark, text-witch-amber, or border-witch-plum.
Opacity Variants
Tailwind’s slash-opacity syntax is used extensively throughout the codebase to layer transparency over the saturated token colors. The table below lists the variants compiled intomain.css.
| Utility | Alpha | Common Context |
|---|---|---|
witch-plum/20 | 12% | Background washes on hover states |
witch-plum/30 | 19% | Border overlays, inactive dividers |
witch-plum/50 | 31% | Mid-weight borders |
witch-plum/60 | 38% | Stronger border accents |
witch-turquoise/20 | 12% | Subtle teal background fill |
witch-turquoise/30 | 19% | Lighter border tones |
witch-moonlight/40 | 25% | Dimmed text on dark cards |
witch-moonlight/60 | 38% | Secondary body text |
witch-moonlight/70 | 44% | Caption and metadata text |
witch-moonlight/80 | 50% | Near-standard text on dark surfaces |
witch-amber/10 | 6% | Faint amber background tint |
witch-amber/20 | 12% | Amber gradient starts |
witch-dark/30 | 19% | Translucent overlay panels |
witch-dark/80 | 50% | Nav and modal backdrops |
bg-witch-plum/30 or text-witch-moonlight/60.
Glow Utilities
Three custom utility classes defined at the bottom ofmain.css apply text-shadow and box-shadow glows that reinforce the candle-lit atmosphere.
.text-glow-amber— Applied to active navigation labels and section headings to simulate candlelight spill..text-glow-teal— Applied to turquoise-tinted decorative text and terminal-style labels..box-glow-plum— Applied to card borders and modal containers to give them an arcane purple halo.
Parchment Background
The.parchment-bg utility combines a near-black fill with an inline SVG fractal-noise texture rendered at 5% opacity. It is used on modal panels and the blog post reader.
<feTurbulence type="fractalNoise" baseFrequency="0.8" numOctaves="4"> to generate the grain. The texture is embedded as a data URI so no external image request is made.
Color Hierarchy
The six tokens form a layered hierarchy from deepest background to brightest interaction signal.witch-dark— Foundation layer. The near-black canvas that every other token sits on. Used forbody, card backgrounds, and the navigation bar fill.witch-plum— Structural layer. Deep purple frames the content through borders, dividers, and ambient blob glows. It marks boundaries without drawing the eye away from content.witch-turquoise— Interaction layer. Bright teal signals clickable and active surfaces — buttons, links, the scrollbar thumb, and focused input borders.witch-amber— Highlight layer. Warm amber is reserved for the highest-priority active state: the current-page flame in the navigation, candle wicks, and hover text on dark cards.witch-moonlight— Reading layer. Cool off-white sits above everything as the default text color, legible against all darker tokens.witch-teal— Echo layer. A slightly darker sibling of turquoise used for secondary accents, hover states on the scrollbar, and the teal text-glow utility.
Changing Colors
All color values are currently baked into the compiled
assets/main.css. The
Tailwind utility classes — including the six witch-* token names — are
resolved at build time from tailwind.config.js. To change any token, you
must edit the original source config and rebuild with npm run build. Editing
main.css directly will be overwritten on the next build.theme.extend.colors block in tailwind.config.js and change the hex value for the token you want to modify, then run the build: