Unified Communications
-
- Voice, meetings, and messaging that keep your people connected without adding operational friction.
-diff --git a/.gitignore b/.gitignore index cae78f4..8bd7eec 100644 --- a/.gitignore +++ b/.gitignore @@ -1,5 +1,28 @@ -DEVELOPMENT_LOG.md -PROJECT.md -STRUCTURE.md -FUTURE.md -HISTORY.md +# Project docs managed in repo unless explicitly excluded elsewhere + +# Dependencies +node_modules/ + +# Build output +dist/ + +# Runtime/database artifacts +db/*.db +db/*.db-* + +# Environment/local files +.env +.env.* +!.env.example + +# Logs +*.log +npm-debug.log* +yarn-debug.log* +yarn-error.log* +pnpm-debug.log* + +# OS/editor +.DS_Store +.vscode/ +.idea/ diff --git a/BUILD_SUMMARY.md b/BUILD_SUMMARY.md new file mode 100644 index 0000000..2fcd9a6 --- /dev/null +++ b/BUILD_SUMMARY.md @@ -0,0 +1,125 @@ +# Queue North Website — Build Summary + +## Completed Tasks + +### Phase 1: Foundation +- ✅ Vite + React + Tailwind setup +- ✅ React Router with all required routes +- ✅ Express backend with /api/health, /api/leads, /api/support +- ✅ SQLite database with leads and support_requests tables +- ✅ TypeScript type definitions via @types packages + +### Phase 2: UI Components +- ✅ Layout components: Header, Footer, MobileNav +- ✅ shadcn/ui-style primitives: Button, Card, Input, Textarea, Select, Badge, Sheet +- ✅ TanStack Query provider for server state +- ✅ Sonner for toast notifications +- ✅ Lucide React for icons + +### Phase 3: Pages +- ✅ Home page with hero, services preview, industries, CTAs +- ✅ About page +- ✅ Services page and individual service detail pages +- ✅ Industries page and individual industry detail pages +- ✅ 8x8 partner page +- ✅ Contact page with form submission to /api/leads +- ✅ Support page with form submission to /api/support + +### Data Files +- ✅ Services data (7 services with full descriptions) +- ✅ Industries data (4 industries with pain points/solutions) + +### Scripts +- ✅ npm run dev (frontend + backend concurrently) +- ✅ npm run build (production build) +- ✅ npm run preview +- ✅ npm run server + +## Test Results + +``` +$ npm run build +✓ built in 1.10s +dist/index.html 0.99 kB +dist/assets/index-CsZTyVVr.css 20.07 kB +dist/assets/index-G07G4G_D.js 333.59 kB +``` + +``` +$ npm run server +Server running on http://localhost:3001 +Health check: http://localhost:3001/api/health +{"status":"ok","timestamp":"2026-05-12T05:48:42.213Z"} +``` + +## Next Steps (for Scarlett) + +1. Run `npm run dev` to start both frontend and backend servers +2. Test the application in browser at http://localhost:5173 +3. Verify all routes work correctly +4. Test contact form submission +5. Test support form submission +6. Check mobile responsiveness +7. Run `npm run build` to verify production build + +## Known Issues / Limitations + +- Sheet component doesn't use TypeScript generics (simplified for build) +- Image assets need to be updated from actual Queue North branding +- The database creates in `db/` directory which should be .gitignored +- Consider adding rate limiting for API endpoints + +## Files Created/Modified + +### New Files: +- `server/index.js` - Express backend +- `server/db/schema.sql` - SQLite schema (created on first run) +- `src/router.jsx` - React Router configuration +- `src/lib/api.js` - API helper with TanStack Query +- `src/lib/queryClient.js` - QueryClient configuration +- `src/data/services.js` - Services data +- `src/data/industries.js` - Industries data +- All component files in `src/components/` +- All page files in `src/pages/` + +### Modified Files: +- `package.json` - Added dependencies (sonner, @radix-ui/react-dialog, lucide-react) +- `vite.config.js` - Added path alias for @/ imports +- `index.html` - Updated to use proper logo path +- `src/App.jsx` - Added MobileNav component +- `src/App.css` - Updated with proper Tailwind imports +- `tailwind.config.js` - Already had Scarlett's color palette +- `README.md` - Already had overhaul plan context + +## Database Schema + +```sql +CREATE TABLE IF NOT EXISTS leads ( + id INTEGER PRIMARY KEY AUTOINCREMENT, + company TEXT NOT NULL, + name TEXT NOT NULL, + email TEXT NOT NULL, + phone TEXT, + zip TEXT, + message TEXT, + service_interest TEXT, + created_at DATETIME DEFAULT CURRENT_TIMESTAMP +) + +CREATE TABLE IF NOT EXISTS support_requests ( + id INTEGER PRIMARY KEY AUTOINCREMENT, + name TEXT NOT NULL, + company TEXT NOT NULL, + email TEXT NOT NULL, + phone TEXT, + issue TEXT NOT NULL, + priority TEXT DEFAULT 'medium', + created_at DATETIME DEFAULT CURRENT_TIMESTAMP +) +``` + +--- + +Built with 🔒 Security in mind +Data integrity maintained +API contracts documented diff --git a/DEVELOPMENT_LOG.md b/DEVELOPMENT_LOG.md new file mode 100644 index 0000000..87e7c07 --- /dev/null +++ b/DEVELOPMENT_LOG.md @@ -0,0 +1,38 @@ +# Queue-North-Website — Development Log + +## v0.1.0 — Phase 1 Foundation — 2026-05-12 + +**Scarlett** — Design brief and UI polish +- Added the design implementation brief to `OVERHAUL_PLAN.md`. +- Established light-first business palette and layout rules. +- Completed focused UI/accessibility polish after Neo scaffold. +- Added Georgia numeric font token guidance and applied numeric styling to visible trust metric content. +- Improved Sheet/Header accessibility and standardized selected page containers/spacing. +- Confirmed old `styles.css` was used only as legacy context, not ported into the new design. + +**Neo** — Phase 1 implementation +- Built Vite + React + Tailwind foundation. +- Added React Router route structure. +- Added Express backend and better-sqlite3 database integration. +- Added contact/support form API wiring. +- Set package version to `0.1.0` for Phase 1. + +**Bishop** — Verification +- Verified `package.json` version matches Phase 1 (`0.1.0`). +- Verified frontend build with `npm run build`. +- Verified backend health endpoint responds OK. +- Verified required routes and API paths are configured. +- Confirmed `.gitignore` excludes `node_modules/`, `dist/`, and SQLite runtime database files. +- Approved Phase 1 for Ripley commit/push to `dev`. + +**Ripley** — Coordination and final gate +- Verified repository remote and pushed README setup commit. +- Documented phase-based versioning in PROJECT.md, OVERHAUL_PLAN.md, and STRUCTURE.md. +- Documented the phase completion rule: after every verified phase, Ripley commits and pushes to `dev`. +- Running final build/health checks before committing Phase 1. + +## v0.0.1 — 2026-05-11 + +**Ripley** — Project initialized +- Created project directory at `/home/kaspa/.openclaw/Projects/Queue-North-Website/`. +- Set up initial PROJECT.md, STRUCTURE.md, FUTURE.md, HISTORY.md, DEVELOPMENT_LOG.md. diff --git a/FUTURE.md b/FUTURE.md new file mode 100644 index 0000000..88fd046 --- /dev/null +++ b/FUTURE.md @@ -0,0 +1,8 @@ +# Queue-North-Website — Planning + +## Next Items +*Awaiting project requirements from _null.* + +--- + +*Add items here as they are defined. Priority levels: CRITICAL, HIGH, MEDIUM, LOW* \ No newline at end of file diff --git a/HISTORY.md b/HISTORY.md new file mode 100644 index 0000000..3953d55 --- /dev/null +++ b/HISTORY.md @@ -0,0 +1,30 @@ +# Queue-North-Website — Changelog + +## v0.1.0 — Phase 1 Foundation — 2026-05-12 + +### Added +- Rebuilt project foundation on Vite + React SPA with React Router. +- Added Tailwind CSS with Queue North light-first business palette. +- Added shadcn/ui-style local primitives for buttons, cards, inputs, textarea, select, badge, sheet, and dialog usage. +- Added Sonner toast support and TanStack Query provider/API helper. +- Added Express backend with `/api/health`, `/api/leads`, and `/api/support`. +- Added better-sqlite3 storage for `leads` and `support_requests`. +- Added all planned frontend routes for home, about, services, service details, industries, industry details, 8x8, contact, and support. +- Added Phase 1 documentation, build summary, script reference, and phase-based versioning rules. + +### Changed +- Replaced the static HTML/CSS/JS entry with the Vite React entry. +- Updated README to point to `OVERHAUL_PLAN.md` as the design source of truth. +- Standardized versioning so Phase 1 uses `0.1.x`, Phase 2 uses `0.2.x`, and later phases follow the same pattern. +- Added Bishop verification rules and the requirement that Ripley pushes to `dev` after each verified phase. + +### Verified +- `npm run build` passes. +- Backend health endpoint responds successfully at `/api/health`. +- Required routes are configured. +- Contact and support API paths exist and write through SQLite. + +## v0.0.1 — Project Initialization — 2026-05-11 + +### Added +- Project initialized with PROJECT.md, STRUCTURE.md, FUTURE.md, HISTORY.md, DEVELOPMENT_LOG.md. diff --git a/OVERHAUL_PLAN.md b/OVERHAUL_PLAN.md index 66f970f..fd0e2e2 100644 --- a/OVERHAUL_PLAN.md +++ b/OVERHAUL_PLAN.md @@ -603,6 +603,16 @@ theme: { } ``` +### Numeric Typography Rule + +All numbers in the visual design should use **Georgia**. This applies to stats, counters, years, version displays, numeric badges, metrics, and prominent numeric callouts. + +Implementation guidance: + +- Add a reusable Tailwind font family such as `font-numeric` mapped to `Georgia, serif`. +- Use the numeric font only on numeric content. +- Do not switch body text, headings, nav, or general copy to Georgia. + ### Typography Scale ```css @@ -794,6 +804,24 @@ Required primitives from `@/components/ui/`: --- +## Phase-Based Versioning + +Version numbers must correlate directly to the active overhaul phase. + +- **Phase 1** uses `0.1.x` + - First Phase 1 release: `0.1.0` + - Iterations/fixes within Phase 1: `0.1.1`, `0.1.2`, etc. +- **Phase 2** uses `0.2.x` + - First Phase 2 release: `0.2.0` + - Iterations/fixes within Phase 2: `0.2.1`, `0.2.2`, etc. +- **Phase 3** uses `0.3.x` +- **Phase 4** uses `0.4.x` +- **Phase 5** uses `0.5.x` + +Rule: the minor version maps to the phase number; the patch version maps to work inside that phase. Do not use unrelated semantic version bumps during the overhaul. + +--- + ## Migration Phases ## Phase 1: Scaffold the Stack diff --git a/PROJECT.md b/PROJECT.md new file mode 100644 index 0000000..16aa9f0 --- /dev/null +++ b/PROJECT.md @@ -0,0 +1,69 @@ +# Queue North Website + +## Overview +Project: Queue-North-Website +Created: 2026-05-11 +Status: Active (Phase 1 Complete - 0.1.0) +Rebuild Phase: 1 (Vite + React + Express + SQLite) + +## Description +Website for Queue North Technologies — an 8x8 Certified Partner delivering UCaaS, Contact Center, deployment, and managed lifecycle support for SMB and enterprise organizations. + +## Tech Stack (Phase 1) +- **Vite** — build tool and dev server +- **React 19** — SPA with client-side routing via React Router 7 +- **Tailwind CSS** — utility-first styling with custom theme +- **shadcn/ui-style** — component primitives built in +- **Sonner** — toast notifications +- **TanStack Query** — server state management +- **Express** — backend API server +- **better-sqlite3** — local SQLite database + +## Directory Structure (Phase 1) +- `index.html` — Entry point (Vite + React entry) +- `src/main.jsx` — React entry point with QueryClient and Toaster +- `src/App.jsx` — Layout wrapper with Header, MobileNav, Footer +- `src/router.jsx` — React Router configuration +- `src/lib/api.js` — API helper with TanStack Query +- `src/data/services.js` — Services data +- `src/data/industries.js` — Industries data +- `src/components/ui/` — UI primitives (Button, Card, Input, etc.) +- `src/components/layout/` — Header, Footer, MobileNav +- `src/pages/` — Route pages (Home, About, Services, etc.) +- `server/index.js` — Express backend with SQLite +- `db/queuenorth.db` — SQLite database (created on first run) +- `assets/` — Images, icons, logos + +## Git +- **Branch:** `dev` (working), `main` (stable) +- **Remote:** `ssh://forgejo/null/Queue-North-Website.git` + +## Versioning + +Version numbers must correlate to the active overhaul phase. + +- Phase 1 releases use `0.1.x` + - Phase 1 baseline: `0.1.0` + - Phase 1 patches/iterations: `0.1.1`, `0.1.2`, etc. +- Phase 2 releases use `0.2.x` + - Phase 2 baseline: `0.2.0` + - Phase 2 patches/iterations: `0.2.1`, `0.2.2`, etc. +- Phase 3 releases use `0.3.x` +- Phase 4 releases use `0.4.x` +- Phase 5 releases use `0.5.x` + +Do not use unrelated semantic version bumps during the overhaul. The minor number tracks the phase; the patch number tracks changes within that phase. + +## Phase Completion Git Rule + +Push to `dev` after every completed and verified phase. + +- Agents do not touch git. +- Bishop verifies and updates docs. +- Ripley performs final checks, commits, and pushes to `dev`. + +## Conventions +- Follow AGENTS.md for agent dispatch protocol +- Ripley coordinates, Neo codes, Scarlett styles, Bishop verifies, Hudson secures +- All agents read STRUCTURE.md before starting tasks +- Ripley owns git — no agent touches git directly diff --git a/README.md b/README.md index e593b78..1b8477d 100644 --- a/README.md +++ b/README.md @@ -107,10 +107,4 @@ Contact and support forms should submit through Express, save to SQLite, and sho ## 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. +See [OVERHAUL_PLAN.md](./OVERHAUL_PLAN.md) for the full rebuild plan and Scarlett's design implementation brief. diff --git a/SCRIPTS.md b/SCRIPTS.md new file mode 100644 index 0000000..640704f --- /dev/null +++ b/SCRIPTS.md @@ -0,0 +1,57 @@ +# Queue North Website — Script Reference + +Run these from the project root. + +## Install + +```bash +npm install +``` + +## Development + +Start frontend and backend together: + +```bash +npm run dev +``` + +Frontend runs through Vite. Backend runs through Express. + +## Build + +```bash +npm run build +``` + +Creates the production frontend build in `dist/`. + +## Preview Frontend Build + +```bash +npm run preview +``` + +## Start Backend Only + +```bash +npm start +``` + +Equivalent compatibility script: + +```bash +npm run server +``` + +## Health Check + +```bash +curl http://localhost:3001/api/health +``` + +Expected response shape: + +```json +{"status":"ok","timestamp":"..."} +``` diff --git a/STRUCTURE.md b/STRUCTURE.md new file mode 100644 index 0000000..dd14a6b --- /dev/null +++ b/STRUCTURE.md @@ -0,0 +1,56 @@ +# Queue-North-Website — Project Structure + +## Agent Roles + +| Agent | Role | Focus Area | +|-------|------|------------| +| Neo | Backend Coder | Server code, APIs, database, build system | +| Scarlett | UI/Design | Frontend components, Tailwind CSS, layout, visuals | +| Bishop | Verification | Build, runtime tests, documentation, version bumps | +| Private_Hudson | Security | Auth, data exposure, input validation, dependency audit | +| Ripley | Coordinator | Git, deploy, pipeline, task dispatch | + +## Code Ownership +TBD — will be defined as the project takes shape. + +## Key Files +- `PROJECT.md` — Project overview and conventions +- `STRUCTURE.md` — This file. Agent roles, code ownership, critical paths +- `FUTURE.md` — Planning doc (what to build next) +- `HISTORY.md` — Version changelog +- `DEVELOPMENT_LOG.md` — Agent activity log + +## Versioning Rules for Bishop + +Bishop owns verification documentation and must ensure version numbers correlate to the active overhaul phase. + +- Phase 1 uses `0.1.x` + - Phase 1 baseline: `0.1.0` + - Phase 1 follow-up fixes/iterations: `0.1.1`, `0.1.2`, etc. +- Phase 2 uses `0.2.x` + - Phase 2 baseline: `0.2.0` + - Phase 2 follow-up fixes/iterations: `0.2.1`, `0.2.2`, etc. +- Phase 3 uses `0.3.x` +- Phase 4 uses `0.4.x` +- Phase 5 uses `0.5.x` + +Rule: the minor version maps to the phase number; the patch version maps to work inside that phase. Do not use unrelated semantic version bumps during this overhaul. + +Before Bishop marks work verified, Bishop must check: +- `package.json` version follows the active phase +- `PROJECT.md` version/status matches the active phase +- `HISTORY.md` release notes use the same version +- Any verification summary references the correct phase/version + +## Phase Completion Git Rule + +Ripley must push to `dev` after every completed and verified phase. + +- Agents do not touch git. +- Bishop verifies and updates docs. +- Ripley performs final local checks, commits, and pushes to `dev`. +- This applies to Phase 1 (`0.1.x`), Phase 2 (`0.2.x`), and all later phases. + +## Cross-Cutting Concerns +- All agents must read this file before starting any task +- All agents report back to Ripley — no agent-to-agent handoffs \ No newline at end of file diff --git a/index.html b/index.html index 8f64a46..ea78246 100644 --- a/index.html +++ b/index.html @@ -1,768 +1,17 @@ -
- -
-
- - Queue North Technologies is an official 8x8 Certified Partner holding Sales, Sales Engineer, Build, Deployment, and Support Certifications. - We design, implement, and operate secure, scalable communication environments for SMB and enterprise organizations. -
- -
-
-
-
- Architecture, deployment, adoption, and long-term operational support — with documentation and accountability.
-We align platform features to workflows, call flows, and real-world staffing — not marketing checklists.
-Consistent escalation management, change control, and an operator mindset that sticks after go-live.
-- Veteran-owned communications and networking partner focused on reliable, future-ready systems. - We tell you the truth and align technology to operations — not licensing structures. -
-- Modern communication, networking, and support services built around your operations today and your growth tomorrow -
-
- Voice, meetings, and messaging that keep your people connected without adding operational friction.
-
- Customer engagement built with routing, reporting, and workflow control that support real operational performance.
-
- Consistent support, clear accountability, and lifecycle management that keep your environment stable long after deployment.
-
- Straightforward guidance and practical training that help your team use technology with confidence and discipline.
-
- Clean structured cabling that gives your business the physical foundation for reliable communication and growth.
-
- Business Wi‑Fi designed for usable coverage, dependable performance, and fewer support headaches across your environment.
-
- Switching and routing built for stability, visibility, and secure local network performance.
-
- Voice, meetings, and messaging that keep your people connected without adding operational friction.
-
- Customer engagement built with routing, reporting, and workflow control that support real operational performance.
-
- Consistent support, clear accountability, and lifecycle management that keep your environment stable long after deployment.
-
- Straightforward guidance and practical training that help your team use technology with confidence and discipline.
-
- Clean structured cabling that gives your business the physical foundation for reliable communication and growth.
-
- Business Wi‑Fi designed for usable coverage, dependable performance, and fewer support headaches across your environment.
-
- Switching and routing built for secure local performance, clean management, and the operational visibility your business needs.
-
- Voice, meetings, and messaging delivered with documentation, governance, and operational clarity.
-Queue strategy, routing logic, reporting, and workforce workflows built for real performance visibility.
-We stay accountable after go-live — support structure, escalation, and change control that doesn’t fall apart.
-- We focus on sectors where communication, reliability, and integration directly impact operations and customer experience. -
-
- Patient experience, scheduling, and staff coordination with a focus on compliance.
-
- Connect stores, back office, and support teams while improving customer interaction.
-
- Reliable office-to-plant communications including paging and alerting for production environments.
-
- Campus communications and customer-facing communications in tightly regulated environments.
-
- Patient experience, scheduling, and staff coordination with a focus on compliance.
-
- Connect stores, back office, and support teams while improving customer interaction.
-
- Reliable office-to-plant communications including paging and alerting for production environments.
-
- Campus communications and customer-facing communications in tightly regulated environments.
-- If your environment provides no insight or accountability — or support is slow and inconsistent — we can help. - Share a few details and we’ll provide clear direction. -
-- Need to sign up for the Queue North Support Center? Create an account to access our knowledge base and submit support tickets. -
- -Already a member?
- - Sign In - -
-