e4f2a27388
Co-authored-by: Copilot <copilot@github.com>
180 lines
7.6 KiB
TypeScript
180 lines
7.6 KiB
TypeScript
// =============================================================================
|
||
// Novarix Networks — Website Content
|
||
// =============================================================================
|
||
//
|
||
// This is the ONLY file you need to edit to change the words on the website.
|
||
//
|
||
// Editing rules:
|
||
// 1. Anything inside "double quotes" is text shown on the website.
|
||
// 2. Keep the quotes around every piece of text.
|
||
// 3. Each line ends with a comma — leave the commas alone.
|
||
// 4. To add a new service or engagement, copy a whole "{ ... }" block,
|
||
// paste it inside the same square brackets [ ... ], and edit the text.
|
||
// 5. Save the file, then run `npm run build` to publish the changes.
|
||
//
|
||
// See EDITING.md in this folder for a friendlier walk-through with examples.
|
||
// =============================================================================
|
||
|
||
export const site = {
|
||
// ---------------------------------------------------------------------------
|
||
// HERO — the big section at the very top of the page
|
||
// ---------------------------------------------------------------------------
|
||
hero: {
|
||
// Small pill above the headline. Set to "" (empty) to hide.
|
||
badge: "Onboarding new accounts",
|
||
|
||
// Small uppercase line above the headline.
|
||
eyebrow: "Network Consulting · Remote Support · Engineering",
|
||
|
||
// The big headline is split into three parts so one word can be coloured.
|
||
// headlineBefore -> normal text on the left
|
||
// headlineAccent -> the word shown in the brand gradient
|
||
// headlineAfter -> normal text on the right
|
||
headlineBefore: "Network expertise, on tap, for teams running",
|
||
headlineAccent: "production",
|
||
headlineAfter: "infrastructure.",
|
||
|
||
// Paragraph under the headline.
|
||
description:
|
||
"Novarix Networks provides engineering-led consulting, remote support, and architecture services for organisations and service providers that need clear technical ownership of their network.",
|
||
|
||
// Two buttons. `href` can be a section anchor (e.g. "#contact") or a URL.
|
||
primaryCta: { label: "Get in touch", href: "#contact" },
|
||
secondaryCta: { label: "Explore services", href: "#services" },
|
||
},
|
||
|
||
// ---------------------------------------------------------------------------
|
||
// SERVICES — three cards under "What we do"
|
||
// ---------------------------------------------------------------------------
|
||
services: {
|
||
eyebrow: "What we do",
|
||
title: "Services",
|
||
description:
|
||
"We focus on the work we can deliver credibly today — engineering-led consulting, hands-on remote support, and network design for organisations that need an experienced second pair of eyes.",
|
||
|
||
// List of service cards. To add a fourth service, copy one block,
|
||
// paste it inside the [ ... ] and edit. Keep the commas between blocks.
|
||
items: [
|
||
{
|
||
index: "01",
|
||
title: "Network Consulting",
|
||
description:
|
||
"Architecture review, design, and second-opinion engineering for organisations and service providers running production networks.",
|
||
},
|
||
{
|
||
index: "02",
|
||
title: "Remote Network Support",
|
||
description:
|
||
"Hands-on remote support for routing, switching, and firewall environments — incident response, change work, and ongoing operations.",
|
||
},
|
||
{
|
||
index: "03",
|
||
title: "Architecture & Design",
|
||
description:
|
||
"New-build network design, refresh planning, and migration support — from single-site refreshes to multi-site routing topologies.",
|
||
},
|
||
],
|
||
|
||
// Dashed-border line under the cards.
|
||
// Set to "" (empty) to hide it entirely.
|
||
capabilities:
|
||
"BGP, OSPF, IS-IS, MPLS, IPv4 / IPv6, firewalls (Juniper, FortiGate, pfSense), routing platforms (Cisco IOS-XE / IOS-XR, Juniper Junos, Arista EOS, MikroTik RouterOS), and Linux-based networking.",
|
||
},
|
||
|
||
// ---------------------------------------------------------------------------
|
||
// ENGAGEMENTS — three cards under "How we engage"
|
||
// ---------------------------------------------------------------------------
|
||
engage: {
|
||
eyebrow: "Working with us",
|
||
title: "How we engage",
|
||
description:
|
||
"Three engagement models, depending on what you need. Most engagements start with a short scoping conversation — no obligation, no charge.",
|
||
|
||
items: [
|
||
{
|
||
title: "Scoped projects",
|
||
description:
|
||
"Fixed-deliverable engagements with a clear statement of work — designs, audits, migrations, refreshes.",
|
||
},
|
||
{
|
||
title: "Monthly retainer",
|
||
description:
|
||
"An agreed block of remote engineering hours each month for ongoing operations, change work, and on-call cover.",
|
||
},
|
||
{
|
||
title: "Ad-hoc support",
|
||
description:
|
||
"Incident-driven engagements for one-off troubleshooting, escalations, and short pieces of design work.",
|
||
},
|
||
],
|
||
},
|
||
|
||
// ---------------------------------------------------------------------------
|
||
// CONTACT — the dark contact card near the bottom
|
||
// ---------------------------------------------------------------------------
|
||
contact: {
|
||
eyebrow: "Get in touch",
|
||
title: "Let’s talk infrastructure.",
|
||
description:
|
||
"For consulting enquiries, remote support, or scoping a piece of design work — reach out directly. We respond to all business enquiries within one working day.",
|
||
|
||
// The button shows your email address; it also opens the user's mail app.
|
||
email: "hello@novarix.uk",
|
||
|
||
// Small grey line shown next to the email button.
|
||
note: "Replies within one working day.",
|
||
},
|
||
|
||
// ---------------------------------------------------------------------------
|
||
// NAV — links shown in the top header (in order, left to right)
|
||
// ---------------------------------------------------------------------------
|
||
nav: [
|
||
{ label: "Services", href: "#services" },
|
||
{ label: "How we engage", href: "#engage" },
|
||
],
|
||
|
||
// ---------------------------------------------------------------------------
|
||
// FOOTER — at the very bottom of the page
|
||
// ---------------------------------------------------------------------------
|
||
footer: {
|
||
company: "Novarix Networks Limited",
|
||
registered: "Registered in England · Company No. 17047180",
|
||
email: "hello@novarix.uk",
|
||
tagline: "Engineered in the UK",
|
||
// Small link in the footer that re-opens the cookie banner.
|
||
cookiePrefsLabel: "Cookie preferences",
|
||
// Link to the cookie policy page.
|
||
cookiePolicyLabel: "Cookie & Privacy Policy",
|
||
cookiePolicyHref: "/cookies",
|
||
},
|
||
|
||
// ---------------------------------------------------------------------------
|
||
// COOKIE BANNER — the bar that appears at the bottom on first visit
|
||
// ---------------------------------------------------------------------------
|
||
cookies: {
|
||
// Short message shown in the banner. Keep it honest — this site does not
|
||
// currently use any tracking cookies, only one preference for consent.
|
||
message:
|
||
"Heads up — this site stores one tiny browser preference to remember your cookie choice. We don’t run analytics, advertising, or third-party tracking.",
|
||
|
||
// The two buttons. Labels are small jokes for network folk; subtitles
|
||
// and aria-labels make them clear to everyone else.
|
||
accept: {
|
||
label: "ACK",
|
||
subtitle: "Allow",
|
||
ariaLabel: "Accept cookies",
|
||
tooltip: "Acknowledged — preference saved",
|
||
},
|
||
reject: {
|
||
label: "RST",
|
||
subtitle: "Decline",
|
||
ariaLabel: "Reject cookies",
|
||
tooltip: "Connection reset — preference declined",
|
||
},
|
||
|
||
// Inline link to the policy page from the banner.
|
||
policyLabel: "Read the policy",
|
||
policyHref: "/cookies",
|
||
},
|
||
} as const;
|