Tailwind CSS is the styling backbone of Digital Domain. Rather than hand-authoring CSS, every layout decision, color, spacing value, and shadow effect is expressed through Tailwind utility classes — compiled into the singleDocumentation Index
Fetch the complete documentation index at: https://mintlify.com/apursley2012/digital-domain/llms.txt
Use this file to discover all available pages before exploring further.
assets/main.css bundle that ships with the repo. The project extends Tailwind’s default theme with a set of retro-specific design tokens: custom color names, Win98-accurate bevel shadows, and an SVG checkerboard background. This page documents every custom token and shows you how to modify them.
The committed repository is a pre-built static site. There is no
tailwind.config.js, package.json, vite.config.js, or src/ directory in the repo — these files were used during the original build but were not committed. All code blocks on this page are example configurations for users who want to fork the project and rebuild it from scratch with their own Vite + Tailwind setup.Custom Color Tokens
The following colors are registered as Tailwind theme extensions and are available astext-*, bg-*, and border-* utility classes throughout the codebase.
| Token | Hex Value | Available Classes | Notes |
|---|---|---|---|
retro-purple | #4B0082 | text-retro-purple, bg-retro-purple | Deep indigo used for page headings |
retro-pink | #FF1493 | text-retro-pink, bg-retro-pink | Hot pink for CTAs, decorations, hover states |
retro-teal | #008B8B | text-retro-teal, bg-retro-teal | Sub-headings and teal accents |
retro-turquoise | #00CED1 | text-retro-turquoise | Winamp text, body background fill color |
retro-yellow | #FFFF00 | text-retro-yellow, bg-retro-yellow, border-retro-yellow | Marquee text, tech badges, guestbook header |
win-gray | #C0C0C0 | text-win-gray, bg-win-gray, border-win-gray | Foundational Win98 panel and button gray |
titlebar | linear-gradient(90deg, navy, #1084d0) | bg-titlebar | All window title bars — a CSS gradient, not a flat color |
bg-[#008080] (a pure teal, slightly darker than retro-teal) is used as an inline arbitrary value for the Skills page desktop background — it is not a named token.
Custom Shadow Utilities
The Win98 aesthetic depends entirely on multi-layerinset box shadows that simulate the classic beveled border look. Digital Domain defines four shadow utilities for this purpose.
shadow-win-out — Raised Panel
Used on window frames, panels, and any element that should appear to protrude from the surface.
shadow-win-in — Sunken / Inset Panel
Used on text inputs, content wells, and areas that should appear pressed into the surface.
shadow-win-btn — Standard Button (Unpressed)
Applied to BeveledButton and any interactive control in its default resting state.
shadow-win-btn-active — Active Button (Pressed)
Applied via active:shadow-win-btn-active to reverse the bevel on click, giving the physical “pushed in” illusion.
Background Pattern
The page background is defined inmain.css at the :root level and applied to body:
--retro-bg variable is an inline SVG data URI that creates a 32×32 checkerboard tile. Each checker square is #008B8B (retro-teal) at 20% opacity, layered over the solid #00CED1 (retro-turquoise) base. To change the pattern color, update the fill hex value in the SVG (encoded as %23RRGGBB). To remove the pattern entirely, delete background-image: var(--retro-bg) from the body rule.
Example Tailwind Config
If you fork this project and set up your own Vite + Tailwind build environment, the followingtailwind.config.js recreates all the custom tokens used in the original build. This file does not exist in the committed repo.
titlebar gradient is not a standard Tailwind color token — it uses Tailwind’s backgroundImage extension instead:
The committed repo ships a pre-compiled
assets/main.css and has no package.json, tailwind.config.js, or src/ directory. To rebuild with modified tokens you must first scaffold a new Vite + Tailwind project, copy the source components into it, add a tailwind.config.js like the example above, then run npm run build. The compiled output can then be committed to replace the existing assets/main.css.