orbit-lunar-pulse-DESIGN.md
Orbit • Lunar Pulse
Orbit Lunar FAQ Section is designed for building reusable UI components in modern web projects. Key features include reusable structure, responsive behavior, and production-ready presentation. It is suitable for component libraries and responsive product interfaces.
HTML Preview
orbit-lunar-pulse.html
DESIGN.md
Prompt context source
| Frontmatter | Value |
|---|---|
| version | "neuform-pro" |
| name | "Orbit • Lunar Pulse" |
| description | "Orbit Lunar FAQ Section is designed for building reusable UI components in modern web projects. Key features include reusable structure, responsive behavior, and production-ready presentation. It is suitable for component libraries and responsive product interfaces." |
| colors | token group |
| primary | "#FF4500" |
| secondary | "#FFFFFF" |
| accent | "#FF4500" |
| background | "#FFFFFF" |
| surface | "#D4D4D4" |
| text-primary | "#111827" |
| text-secondary | "#4B5563" |
| border | "#D4D4D4" |
| typography | token group |
| display-lg | token group |
| body-md | token group |
| label-md | token group |
| spacing | token group |
| base | "8px" |
| gap | "16px" |
| card-padding | "24px" |
| section-padding | "80px" |
| rounded | token group |
| card | "8px" |
| control | "8px" |
| pill | "9999px" |
| components | token group |
| card | token group |
| button | token group |
Orbit • Lunar Pulse
Source: Neuform Pro templates. Author: Sourasith Phomhome (@madebysourasith). Views: 54; favorites: 10; remixes: 2.
Tags: faq, section, animated, threejs, navigation, links, support, action.
Overview
Orbit Lunar FAQ Section is designed for building reusable UI components in modern web projects. Key features include reusable structure, responsive behavior, and production-ready presentation. It is suitable for component libraries and responsive product interfaces.
Orbit Lunar Pulse Schedule The Ritual Access Faq Jul–Aug 2026 • Montréal Get Tickets Open-air salsa nights • Rotating Montréal parks Music brings strangers together — one park at a time. • Jul–Aug 2026 / • Montréal Next…
Composition
Use the attached HTML reference as the source of truth. Preserve the visible hierarchy, first-screen composition, section rhythm, density, and interaction tone before adapting copy or content.
Key visible headings include: Dance under the city lights.; ORBIT; LUNAR; PULSE.
Colors
Anchor the palette in primary #FF4500, secondary #FFFFFF, accent #FF4500, background #FFFFFF, surface #D4D4D4, text-primary #111827. Keep background, surface, text, and border roles distinct so generated layouts retain the same contrast pattern as the source.
Typography
Use Inter for display moments and Inter for body copy unless the HTML clearly demands a compatible fallback. Labels and technical metadata should use JetBrains Mono or an equivalent mono face.
Layout
Keep spacing deliberate and stable. Favor the same grid direction, max-width behavior, card density, and responsive stacking seen in the HTML. Do not replace distinctive source structures with generic SaaS sections.
Components
Cards, buttons, badges, navigation, and repeated blocks should preserve the source geometry, border treatment, and hover feel.
Motion
Preserve existing motion cues such as masked reveals, staggered entrance, hover lift, scroll-triggered transitions, and ambient movement. Keep easing smooth and restrained.
WebGL & Effects
If the source includes canvas, WebGL, Three.js, gradients, particles, or atmospheric effects, rebuild them as supporting layers behind the content. Keep effects performant, responsive, and secondary to the interface.
Guardrails
- Do not flatten the source into a generic card grid.
- Do not swap the color mode unless the source clearly supports it.
- Preserve the first viewport signal, focal object, and visual density.
- Keep buttons, cards, and badges aligned to the same radius and border language.