Aurora Drift ships with placeholder text, initials, and a specific turquoise-and-navy colour palette. Some of those choices live in files you can edit directly inside the compiled repository — no build step required. Others are baked into the Tailwind-generated CSS and require the original Vite source to change properly. The steps below are split accordingly so you always know exactly what you can edit right now.Documentation Index
Fetch the complete documentation index at: https://mintlify.com/apursley2012/aurora-drift/llms.txt
Use this file to discover all available pages before exploring further.
The Aurora Drift repository contains compiled Vite build output — the
assets/, components/, and pages/ directories hold bundled JavaScript and CSS, not raw JSX source files. Steps 1–4 and step 6 below work directly on those compiled files. Steps that require the original source (hero text, project data, Tailwind colour tokens) are labelled clearly.Replace the hero text
The home page hero heading and subtitle are compiled into
assets/main.js, which is a minified bundle and cannot be edited safely by hand. To change the hero copy you need the original Vite source project (typically src/App.jsx or src/pages/Home.jsx). Locate the JSX that renders the large display heading and the tagline paragraph, swap the placeholder strings for your own, then run npm run build to regenerate the bundle.Update the nav name
Open The
components/Nav.js directly in the compiled repository. The logo area renders the string "N.L." — find that string and replace it with your own initials or a short name. The glowing turquoise dot that follows the initials is rendered by the same component; you can remove it or keep it.navLinks array is also declared in this file. Each entry has a path and a label key. You can reorder entries or update label values here without rebuilding.Edit aurora wave colours
The animated background waves are drawn in The wave paths animate continuously via Framer Motion — the colour change takes effect as soon as you save the file, with no rebuild needed.
components/AuroraBackground.js using three SVG <linearGradient> elements with IDs aurora1, aurora2, and aurora3. Each gradient has three stopColor values you can change directly in this compiled file:Changing Tailwind colour tokens (e.g.
aurora-turquoise, aurora-cyan) used in utility classes elsewhere in the app requires editing tailwind.config.js in the original source project and rebuilding. Those tokens are not accessible in the compiled output.Change the cursor glow colour
The custom cursor is rendered in The component only activates on devices where
components/CursorGlow.js. It uses a radial-gradient applied to a 300 × 300 px absolutely positioned element. Find the background style property and change the RGBA colour values:pointer: fine is detected (mouse-driven devices), so mobile visitors are unaffected.Replace project, blog, and work content
The Projects, Blog, Work, and Case Studies page data is compiled into
assets/main.js and cannot be edited safely in the compiled output. To update this content you need the original Vite source project. Locate the data arrays in the relevant page component files (e.g. src/pages/Projects.jsx), replace the placeholder objects with your own entries, and run npm run build to regenerate the bundle.Each entry typically contains fields such as title, description, tags, date, and href. The grid layout reflows automatically as you add or remove entries.Update fonts
Fonts are loaded via a Google Fonts Replace the
@import at the very top of assets/main.css. This file is safe to edit directly:@import URL with a new one from fonts.google.com to swap typefaces. Note that font-family references in the compiled Tailwind output use the tokens Instrument Serif (for headings, set via font-serif) and the system sans-serif stack for body text — updating those references requires the original source project.