docs: add Queue North website objective
This commit is contained in:
parent
b7dfee3023
commit
c8307e61d6
|
|
@ -0,0 +1,116 @@
|
||||||
|
# Queue North Website
|
||||||
|
|
||||||
|
## Objective
|
||||||
|
|
||||||
|
Queue North Website is the modern rebuild of the Queue North Technologies business website.
|
||||||
|
|
||||||
|
The goal is to replace the current static early-2000s-style HTML/CSS/JS site with a polished 2026 business website that clearly presents Queue North as a trustworthy communications, contact center, networking, and managed support partner.
|
||||||
|
|
||||||
|
The site should feel:
|
||||||
|
|
||||||
|
- Bright and professional
|
||||||
|
- Modern but not flashy
|
||||||
|
- Business-first, not cyber/gaming/crypto
|
||||||
|
- Easy to navigate
|
||||||
|
- Clear about Queue North's 8x8 partnership and service expertise
|
||||||
|
- Optimized for consultation and support request conversion
|
||||||
|
|
||||||
|
## Target Stack
|
||||||
|
|
||||||
|
- **Vite** — build tool, not Next.js
|
||||||
|
- **React** — SPA frontend
|
||||||
|
- **React Router** — client-side routing
|
||||||
|
- **Tailwind CSS** — utility-first styling
|
||||||
|
- **shadcn/ui** — component primitives
|
||||||
|
- **Sonner** — toast notifications
|
||||||
|
- **TanStack Query** — server state management
|
||||||
|
- **Express** — backend API
|
||||||
|
- **better-sqlite3** — SQLite database
|
||||||
|
|
||||||
|
## Layout Direction
|
||||||
|
|
||||||
|
The design direction is a light-first B2B technology layout with strategic dark navy sections.
|
||||||
|
|
||||||
|
Primary structure:
|
||||||
|
|
||||||
|
1. **Hero**
|
||||||
|
- Dark navy section
|
||||||
|
- Clear headline and value proposition
|
||||||
|
- Primary CTA: `Request Consultation`
|
||||||
|
- Secondary CTA: `Explore Services`
|
||||||
|
- Trust chips: 8x8 Certified Partner, Veteran Owned, 25+ Years Experience, SMB to Enterprise
|
||||||
|
|
||||||
|
2. **Trust / Certification Bar**
|
||||||
|
- Light section
|
||||||
|
- Reinforces 8x8 partner credibility
|
||||||
|
|
||||||
|
3. **Services Preview**
|
||||||
|
- White cards on a bright background
|
||||||
|
- Concise service explanations
|
||||||
|
- Links to service detail pages
|
||||||
|
|
||||||
|
4. **Why Queue North**
|
||||||
|
- Three-pillar section:
|
||||||
|
- Architecture
|
||||||
|
- Deployment
|
||||||
|
- Lifecycle Support
|
||||||
|
|
||||||
|
5. **Industries**
|
||||||
|
- Healthcare
|
||||||
|
- Retail
|
||||||
|
- Manufacturing
|
||||||
|
- Education & Finance
|
||||||
|
|
||||||
|
6. **Final CTA**
|
||||||
|
- Dark navy conversion band
|
||||||
|
- Consultation-focused message
|
||||||
|
|
||||||
|
## Planned Routes
|
||||||
|
|
||||||
|
```txt
|
||||||
|
/
|
||||||
|
/about
|
||||||
|
/services
|
||||||
|
/services/unified-communications
|
||||||
|
/services/contact-center
|
||||||
|
/services/managed-support
|
||||||
|
/services/consulting-training
|
||||||
|
/services/infrastructure-cabling
|
||||||
|
/services/wireless-access
|
||||||
|
/services/local-networking
|
||||||
|
/industries
|
||||||
|
/industries/healthcare
|
||||||
|
/industries/retail
|
||||||
|
/industries/manufacturing
|
||||||
|
/industries/education-finance
|
||||||
|
/8x8
|
||||||
|
/contact
|
||||||
|
/support
|
||||||
|
```
|
||||||
|
|
||||||
|
## Backend Goals
|
||||||
|
|
||||||
|
Initial API endpoints:
|
||||||
|
|
||||||
|
```txt
|
||||||
|
GET /api/health
|
||||||
|
POST /api/leads
|
||||||
|
POST /api/support
|
||||||
|
```
|
||||||
|
|
||||||
|
Initial SQLite tables:
|
||||||
|
|
||||||
|
- `leads`
|
||||||
|
- `support_requests`
|
||||||
|
|
||||||
|
Contact and support forms should submit through Express, save to SQLite, and show user feedback with Sonner.
|
||||||
|
|
||||||
|
## Design Source of Truth
|
||||||
|
|
||||||
|
See:
|
||||||
|
|
||||||
|
- `OVERHAUL_PLAN.md`
|
||||||
|
- `STRUCTURE.md`
|
||||||
|
- `PROJECT.md`
|
||||||
|
|
||||||
|
`OVERHAUL_PLAN.md` contains the full rebuild plan and Scarlett's design implementation brief.
|
||||||
Loading…
Reference in New Issue