Corp Website Prompt

ACT AS:
A trio-minded design + build lead combining:
- Jony Ive: radical simplicity, material honesty, obsessive craft, “less but better”, calm confidence, exquisite proportion.
- Don Norman: user-centered design, clear affordances, feedback, constraints, error prevention, mental models, usability-first.
- Elizabeth Churchill: human-centered, sociotechnical thinking, trust, inclusion, collaboration, content credibility, responsible AI, ethics.

MISSION:
Redesign and rebuild the Redinent global website (current reference: global.redinent.com) into a clean, Apple-like, premium experience that instantly communicates what Redinent is building and selling—AI-enabled cyber-physical security intelligence for IoT, OT/ICS, Data Centers, and AI Infrastructure—while proving ROI and building trust for enterprise buyers.

CORE OUTCOME (ONE-GLANCE CLARITY):
Within 5 seconds, a visitor must understand:
1) WHAT: “AI-enabled cyber-physical security intelligence platform”
2) WHO: “Enterprises running IoT + OT/ICS + Data Centers + AI Infrastructure”
3) WHY: “Deep asset intelligence + contextual risk + threat intelligence → faster decisions, reduced exposure, audit-ready reporting”
4) NEXT STEP: “Request a demo” (primary) and “Talk to an expert” (secondary)

DESIGN PRINCIPLES (NON-NEGOTIABLE):
Jony Ive lens (craft & reduction)
- Remove everything non-essential. Use whitespace as a structural element.
- Perfect typographic hierarchy, consistent rhythm, precise alignment, generous margins.
- Subtle motion only to support understanding, never decoration.
- Honest visuals: abstract gradients, clean diagrams, device silhouettes; no “hacker stock photos”.

Don Norman lens (usability & comprehension)
- Clear information scent: navigation labels match user vocabulary (Platform, Solutions, ROI, Research, Company, Contact).
- Strong affordances: buttons look clickable, links look like links, forms are forgiving.
- Feedback and state: active nav, form validation, loading states, clear success messaging.
- Error prevention: inline examples, constraints, sensible defaults, reduced cognitive load.
- Progressive disclosure: show the essentials first; allow deeper technical detail on demand.

Elizabeth Churchill lens (trust, inclusion, responsible AI)
- Trust-building: transparent claims, clear disclaimers, credible research posture, privacy-by-design tone.
- Inclusive language, accessible contrast, keyboard-first navigation, readable line lengths.
- Sociotechnical clarity: show how teams work with the platform (CISO, SecOps, OT engineers, IT admins).
- Responsible AI framing: “assistive intelligence” with explainability (evidence, sources, confidence).

TONE OF VOICE:
Crisp, calm, precise, outcome-led. Avoid hype. Use “evidence-backed”, “context-aware”, “at scale”.
No unverified superlatives. If numeric claims are used, mark them as “example” or “varies by environment”.

AUDIENCES & JOBS-TO-BE-DONE (MUST DESIGN FOR):
Primary personas:
- CISO / Security Director (risk posture, board reporting, ROI, compliance)
- SecOps Lead (workflow, alerts, integrations, speed)
- OT/ICS Engineer (safety, uptime, low disruption, asset visibility)
- Data Center Ops / Infra Lead (inventory accuracy, exposure, patch coordination)
- AI Platform Owner (GPU clusters, orchestration stacks, supply chain/firmware, visibility)

Primary jobs:
- “Know what assets we actually have” (including true OEM detection / deep profiling)
- “Know what is exploitable and urgent”
- “Prioritize remediation without disrupting operations”
- “Prove risk reduction and ROI”
- “Integrate with existing tools and workflows”

SCOPE (FULL SITE REVAMP):
Revamp all pages with richer detail on AI, IoT, OT, Data Center, AI Infrastructure, and ROI.
Keep and improve existing themes: Deep Asset Intelligence, Vulnerability Intelligence, Threat Intelligence, Enterprise Integrations, Research/CVEs, Resources, Press, About, Careers, Partners, Contact.
Make differentiation explicit and easy to understand.

TECH STACK REQUIREMENTS:
- Next.js 14+ (App Router), TypeScript
- Tailwind CSS with CSS variables and light/dark mode (system default)
- Framer Motion (minimal)
- Content: Headless CMS recommended (Sanity preferred) OR structured JSON for easy migration
- Forms: server actions/API + honeypot + basic rate-limit
- Analytics placeholders: GA4/Plausible
- Hosting: Vercel

NEW INFORMATION ARCHITECTURE (ROUTES):
1) Home
2) Platform (overview)
   - Deep Asset Intelligence
   - Vulnerability Intelligence
   - Threat Intelligence
   - Enterprise Integrations
3) Solutions
   - IoT Security
   - OT/ICS Security
   - Data Center Security
   - AI Infrastructure Security
4) Industries
   - Manufacturing
   - Energy & Utilities
   - Smart Buildings / Smart Cities
   - BFSI
   - Healthcare
   - Government & Defense
5) ROI / Outcomes
   - ROI Overview
   - ROI Calculator (interactive)
   - Case Studies (list + template)
   - Compliance & Audit Readiness (aligned reporting; avoid legal claims)
6) Research
   - Research Overview
   - CVE Index
   - CVE Detail Template
   - Responsible Disclosure Policy (recommended)
7) Resources
   - Articles / Insights
   - Whitepapers (optional gating)
8) Company
   - About
   - Leadership & Advisors
   - Press
   - Careers
   - Partner Program
9) Contact / Request Demo

NAVIGATION REQUIREMENTS:
- Sticky header, compact, premium.
- “Platform” and “Solutions” use a tasteful mega-menu with 2–3 columns:
  - short descriptors + 1-line outcome per item.
- Persistent primary CTA: “Request demo”.
- Secondary: “Talk to an expert”.

HOME PAGE (APPLE-LIKE SCROLL STORY) — MUST BUILD EXACTLY:
1) Top Nav (sticky)
2) Hero (clean, strong statement)
   - Headline: “AI-enabled cyber-physical security intelligence.”
   - Subhead: “Protect IoT, OT/ICS, data centers, and AI infrastructure with deep asset intelligence, contextual risk, and real-time threat signals.”
   - CTAs: Request demo (primary), Explore platform (secondary)
   - Background: subtle gradient/noisy texture, no clutter
3) One-glance clarity strip (4 chips):
   - Know what you own (true OEM detection)
   - Validate what’s exploitable (evidence-backed risk)
   - Prioritize what matters (context-aware scoring)
   - Act fast (integrations + workflows)
4) “One platform” module (4 pillar cards, link out)
5) Solutions by domain (tabbed or scroll-snap)
   For each: key risks → what Redinent does → outcomes
6) “How it works” narrative (Discover → Assess → Prioritize → Remediate → Monitor)
7) ROI teaser (3 outcome statements + CTA “Calculate ROI”)
   Include footnote: “Results vary by environment.”
8) Trust & proof (logos/awards placeholders, 1–2 testimonials, research credibility)
9) Research highlight (latest CVEs/insights cards)
10) Final CTA band + short demo form
11) Footer (full sitemap, locations, privacy/terms)

PLATFORM OVERVIEW PAGE:
- Hero: “Actionable intelligence for connected environments.”
- Explain pillars and how they connect.
- Include simple SVG architecture diagram:
  discovery → intelligence engines → dashboards/reports → integrations
- Deployment model section: cloud/hybrid/on-prem (keep generic)
- Outputs: executive report, technical evidence report, continuous monitoring alerts
- CTA: Request demo

PILLAR PAGES (4):
A) Deep Asset Intelligence
- Deep profiling, true OEM detection, passive + active discovery (non-disruptive language)
- What you get: fingerprint evidence, device attributes, lifecycle signals (if available), business tags
- Visual mock: “device card” + “evidence panel”
B) Vulnerability Intelligence
- Evidence-backed validation, contextual prioritization, remediation workflows
- “Virtual Red Team” concept framed carefully: continuous validation methods
- ROI block focused on time saved and reduced noise
C) Threat Intelligence
- Real-time signals mapped to assets, exposure monitoring, curated intel
- “Signal to action” flow → integrations
D) Enterprise Integrations
- Categories: ITSM, SIEM/SOAR, CMDB, SSO/IAM, Cloud
- Integration patterns: push findings, enrich events, automate tickets, export reports
- Governance posture statements only as “supports/aims” unless confirmed

SOLUTIONS PAGES (4) — TEMPLATE:
- Domain hero + 3 pains + 3 outcomes
- Typical assets list
- How Redinent helps mapped to the 4 pillars
- ROI section (savings categories)
- 1 mini-case study teaser + relevant research links
Domains:
- IoT Security
- OT/ICS Security (stress safety/uplink constraints + non-disruptive scanning)
- Data Center Security
- AI Infrastructure Security (GPU servers, orchestration stacks, edge AI)

ROI / OUTCOMES:
1) ROI Overview Page
- Explain ROI categories:
  - faster assessments
  - reduced manual validation
  - reduced downtime risk
  - improved prioritization / MTTR
  - tool + workflow consolidation (integrations)
- Add “Value proof” blocks: case studies + reporting examples
2) ROI Calculator Page (interactive)
Inputs:
- # sites
- estimated connected assets (IoT + OT + DC + AI infra)
- security team size
- assessment frequency
- avg hours per assessment cycle
- hourly cost
Optional:
- downtime cost per hour
- current tool costs
Outputs:
- hours saved/year
- estimated cost savings/year
- payback period (simple)
- qualitative “risk posture improvement” indicator (avoid fake precision)
Disclaimer: “Estimates vary; confirm with Redinent specialist.”

RESEARCH:
- Research overview: credibility, methodology, disclosure stance
- CVE index: filter by year/vendor/severity
- CVE detail template: summary, impact, affected products, mitigations, timeline, references
- Add structured data: Article/TechArticle

RESOURCES:
- Articles with categories: AI, IoT, OT, Data Center, Firmware, Supply Chain
- Reading time, author, date, related content
- Optional whitepaper gating with respectful UX

COMPANY:
- About: mission, story, values, global presence
- Leadership & Advisors: cards
- Press: releases + media kit placeholder
- Careers: culture + openings
- Partner Program: partner types + benefits + apply CTA

CONTACT / REQUEST DEMO:
- Clean form, strong validation, non-annoying friction
- Add scheduling embed placeholder
- Locations: India, Australia

ACCESSIBILITY + PERFORMANCE (MUST IMPLEMENT):
- WCAG AA contrast, focus states, keyboard navigation, skip-to-content
- Next/Image optimization, lazy load, minimal JS
- Lighthouse target 90+ across categories

SEO:
- Unique titles + meta descriptions
- OG/Twitter cards
- canonical, sitemap.xml, robots.txt
- Schema: Organization, WebSite, BreadcrumbList, Article/TechArticle

DELIVERABLES YOU MUST OUTPUT IN ONE RESPONSE:
1) Sitemap + navigation model (including mega-menu layout)
2) Wireframe-level section breakdown for:
   - Home
   - Platform overview + each pillar page
   - Each Solutions page
   - ROI overview + ROI calculator
   - Case studies list + case study template
   - Research listing + CVE detail template
   - Resources list + article template
   - Company pages
   - Contact/demo
3) Design system tokens (Tailwind theme variables: colors, typography scale, spacing, radii, shadows)
4) Component inventory list (React components + responsibility)
5) Content model (CMS-ready types + fields) + sample JSON for:
   - one article
   - one CVE entry
   - one case study
6) Next.js app router scaffold + key file skeletons (pages + layout + components)
7) ROI calculator logic (clear formulas + pseudocode + UI layout)
8) SEO metadata examples (Home + one Solutions page)

CONSTRAINTS:
- No clutter, no cyberpunk, no stock “hacker” visuals.
- No background videos unless extremely subtle + lazy-loaded.
- Keep claims cautious, credible, and user-benefit-focused.

START NOW:
Output the deliverables in the exact order listed above, with clean headings and code blocks where appropriate. Produce implementable Next.js/TS/Tailwind skeleton code, plus structured content JSON, so a developer can paste into an IDE and start building immediately.