NeuraNest AI · Brand & Deploy Reference

The brand,
start to live.

Everything that makes the NeuraNest AI site itself — who it is, the one logo, the five colour profiles, where the files live, and the exact commands to push a new version online. Written so a non-coder can follow it.

1 source folder5 colour profiles1 deploy command
01 · WHO THE BRAND IS

NeuraNest AI, in one place.

The core facts that never change. Use these exact values everywhere — site, decks, emails, invoices.

Brand name
NeuraNest AI
Tagline
"Your data is already telling a story. We help you hear it."
Positioning
Melbourne AI Data Expert · A$299 audit · 5-day SLA
Founder
Khalid Rind — Melbourne, Australia
Contact
neuranest@neuranestai.world · +61 493 348 617
Philosophy
Clarity Before Automation
02 · THE LOGO

One mark. Transparent. Glowing.

There is a single logo: the neural-network mark + the words NeuraNest AI, centred at the top of the page (the "brand strip"). The old small logo in the menu bar has been removed — there is now only one.

logo rules
file
assets/neuranest-mark.png — white network mark on a fully transparent background (no black box).
never
Do not apply a CSS invert() filter. The mark is already white — invert would turn it black and bring the box back.
glow
The glow colour is driven by the CSS variable --glow, so it recolours automatically with the active colour profile.
backup
The previous logo is kept at assets/neuranest-mark-ORIGINAL-backup.png — nothing was destroyed.
03 · THE FIVE COLOUR PROFILES

One palette switch re-skins everything.

Click the 🎨 button (bottom-right) to switch profile. Colours, the menu bar, and the logo glow all change together — the choice is remembered in the browser. Each profile is a single CSS block of variables.

Ocean Deep · default
Classic NeuraNest — teal, deep blue, ember
Quantum Night · data-theme="quantum"
Futuristic — violet, pink, cyan
Midnight Gold · data-theme="midnight"
Executive — gold, amber, ember
Crimson Signal · data-theme="crimson" · NEW
Editorial — bold red authority
Emerald Flux · data-theme="emerald" · NEW
Terminal — calm data green

To add a 6th profile later

Two small edits in index.html, no new files:

index.html
/* 1 · add a variable block in the <style> theme area */
[data-theme="sunset"]{
  --ink:#…; --panel:#…; --ocean:#…; --slate:#…;
  --ember:#…; --gold:#…; --gold-soft:#…; --text:#…; --dim:#…;
  --line:…; --line-soft:…;
  --glow: …; --glow-soft: …;   /* logo glow for this profile */
}

<!-- 2 · add one option in the .dp-panel switcher -->
<div class="dp-opt" data-t="sunset"> … </div>

The switcher JavaScript is generic — it reads data-t automatically, so no script changes are needed.

04 · WHERE THE FILES LIVE

One folder is the whole site.

Everything is in a single source folder on the PC. Editing means opening index.html and changing text or swapping an image.

source folder
folder
C:\AI-AIR-TEAM-HQ\AAI-NEURANEST-PROJECT\AI-PROJECTS-BT-NEURANEST-AI\NEURANEST-AGENCY-WEBSITE\
index.html
The homepage — all sections, styles, the 5 profiles, and the switcher.
guide/index.html
This guide (lives at /guide on the live site).
assets/ images/
Logo mark, favicon, pictures.
firebase.json
Hosting config — leave it alone unless deploying to a different site.
05 · PUSH A NEW VERSION LIVE

The exact commands.

After you change anything, run these in PowerShell. This is the whole deploy — copy it as-is. It publishes to the fresh site neuranestai-agency.web.app.

PowerShell — deploy to neuranestai-agency.web.app
# 1 · make node + firebase visible this session
$env:PATH = "C:\Program Files\nodejs;" + $env:PATH + ";C:\Users\ksr11\AppData\Roaming\npm"

# 2 · go to the source folder
Set-Location "C:\AI-AIR-TEAM-HQ\AAI-NEURANEST-PROJECT\AI-PROJECTS-BT-NEURANEST-AI\NEURANEST-AGENCY-WEBSITE"

# 3 · deploy to the fresh site (uses a dedicated config file)
firebase deploy --only hosting --config firebase.neuranestai-agency.json --project gen-lang-client-0896413040

✓ Hosting URL: https://neuranestai-agency.web.app

Why a separate config file? firebase.neuranestai-agency.json is a copy of the normal config with one extra line — "site": "neuranestai-agency". It lets the fresh site deploy in one command without ever touching the main firebase.json. It already exists in the folder — just run the command above.

Why not a brand-new Firebase project? The Google account cybersmartchoice@gmail.com has hit its project-creation quota, so firebase projects:create fails. We use a fresh hosting site inside an existing project instead — same result, a clean new .web.app link, no quota issue.

Good habit on every change

Bump a small version note + one CHANGELOG line so any AI AIR Team member can see what changed and when. Verify the live URL in a browser after deploy — never assume it worked.

06 · THE DOMAIN (neuranestai.agency)

Expired — but the site never went down.

The custom domain neuranestai.agency expired and is now a parked page. That only broke the domain → site mapping. The actual website is fine and live on Firebase URLs.

To get the real domain back, renew it at the registrar (needs the owner's login), then point its DNS at the Firebase site. Until then, share the fresh .web.app link.

07 · THE ONE RULE

Truth first. Verify before claiming.

Every change is checked against the real files and the live URL before it's called done. No placeholders, never delete the founder's work, only build on what already works. That's the Rind Standard — and it's why this guide only lists things that are actually true today.