feat(web-ng): color scheme change #1090
Labels
No labels
1week
2weeks
Failed compliance check
IP cameras
NATS
Possible security concern
Review effort 1/5
Review effort 2/5
Review effort 3/5
Review effort 4/5
Review effort 5/5
UI
aardvark
accessibility
amd64
api
arm64
auth
back-end
bgp
blog
bug
build
checkers
ci-cd
cleanup
cnpg
codex
core
dependencies
device-management
documentation
duplicate
dusk
ebpf
enhancement
eta 1d
eta 1hr
eta 3d
eta 3hr
feature
fieldsurvey
github_actions
go
good first issue
help wanted
invalid
javascript
k8s
log-collector
mapper
mtr
needs-triage
netflow
network-sweep
observability
oracle
otel
plug-in
proton
python
question
reddit
redhat
research
rperf
rperf-checker
rust
sdk
security
serviceradar-agent
serviceradar-agent-gateway
serviceradar-web
serviceradar-web-ng
siem
snmp
sysmon
topology
ubiquiti
wasm
wontfix
zen-engine
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
carverauto/serviceradar#1090
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Imported from GitHub.
Original GitHub issue: #2978
Original author: @mfreeman451
Original URL: https://github.com/carverauto/serviceradar/issues/2978
Original created: 2026-03-02T05:07:28Z
Is your feature request related to a problem?
The "Nocturne Dashboard" Palette
You need distinct layers of dark to create depth without using heavy shadows.
Base (App Background): #09090B (Almost pitch black, very slight cool tint)
Surface (Cards, Sidebar, Panels): #131316 (Slightly lighter to lift elements off the background)
Surface Highlight (Hover states, borders): #27272A (Used for subtle borders between table rows or panel edges)
Contrast is key for readability in dark mode.
Text Primary (Headings, active stats): #F4F4F5 (Off-white, easier on the eyes than pure #FFF)
Text Muted (Labels, table headers, secondary info): #A1A1AA (A cool gray)
Text Dark (Disabled states): #52525B
These are used sparingly for data visualization (like those charts), buttons, active states, and toggles.
Primary Accent (The Cyan): #00D8FF (Electric Cyan - used for the main graphs, progress bars, and active links)
Primary Glow (Faded Cyan): #004A5C (Used for the gradient fill under the line charts)
Error/Danger (The Magenta): #FF2A7A (Neon Pink/Magenta - used for the "Errors" graph and alerts)
Warning (The Amber): #FF9A00 (Used in the table status indicators)
Success (The Green): #00E676 (Used for the percentage increase text like +87.00%)
How to use this in Phoenix LiveView (Tailwind)
Open your assets/tailwind.config.js file and extend your theme colors like this:
code
JavaScript
module.exports = {
// ... other config (content, plugins, etc.)
theme: {
extend: {
colors: {
// Backgrounds
void: {
base: '#09090B',
surface: '#131316',
border: '#27272A',
},
// Neon Accents
cyber: {
cyan: '#00D8FF',
cyanglow: 'rgba(0, 216, 255, 0.15)', // Great for chart fills or subtle backgrounds
magenta: '#FF2A7A',
amber: '#FF9A00',
green: '#00E676',
}
},
// Optional: Add custom box shadows for that "neon glow" effect
boxShadow: {
'cyan-glow': '0 0 10px rgba(0, 216, 255, 0.3)',
'magenta-glow': '0 0 10px rgba(255, 42, 122, 0.3)',
}
},
},
// ...
}
UI Execution Tips for LiveView
To make your Phoenix app look exactly like this screenshot, keep these styling rules in mind:
Borders over Shadows: Notice how the screenshot doesn't really use drop-shadows to separate the cards. Instead, it uses a 1px solid border (border-void-border).
Tailwind example:
Muted Data, Bright Highlights: Most of your text should be text-zinc-400 (or text-gray-400). Only the actual numbers (like the "13" or "0.02 ms") should be bright white (text-white or text-zinc-100).
The Glow Effect: For progress bars (like those blue ones in the table) or active buttons, use the custom shadow we defined above to give it a slight emissive light effect.
Tailwind example:
Fonts: To complete the look, use a sleek sans-serif font like Inter (which is what standard Phoenix/Tailwind uses) or for a slightly more tech feel, try Geist Sans or JetBrains Mono for the numbers and data points.
Describe the solution you'd like
A clear and concise description of what you want to happen.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.