{
  "meta": {
    "langName": "English",
    "dir": "ltr",
    "title": "homePageCar | Connected rental-car operations",
    "description": "Run reservations, vehicles, agreements, handovers, and returns in one connected rental operations platform."
  },
  "header": {
    "nav": [
      ["product", "Product"],
      ["workflow", "Workflow"],
      ["modules", "Modules"],
      ["pricing", "Pricing"],
      ["faq", "FAQ"]
    ],
    "login": "Log in",
    "demo": "Book a demo",
    "menu": "Open menu",
    "language": "Language",
    "theme": "Theme",
    "light": "Light",
    "dark": "Dark",
    "system": "System"
  },
  "hero": {
    "eyebrow": "Rental operations, connected",
    "title": "Run every rental from reservation to return in one system.",
    "body": "Give reservations, fleet, agreements, handovers, and returns one operational record, so each team sees what needs attention next.",
    "primary": "Book a product demo",
    "secondary": "Watch product tour",
    "caption": "Illustrative product interface. Final screens must use approved product data and captures."
  },
  "trust": {
    "eyebrow": "Operational coverage",
    "title": "One workflow across the rental lifecycle.",
    "body": "Keep the customer, vehicle, agreement, and task context connected as the rental moves forward.",
    "items": [
      ["Reservation", "Capture the request and required details."],
      ["Vehicle", "Track availability and readiness."],
      ["Agreement", "Keep pickup tasks and records together."],
      ["Return", "Record condition and close follow-up work."]
    ]
  },
  "comparison": {
    "eyebrow": "Why change",
    "title": "Replace fragmented handoffs with a shared operating flow.",
    "body": "The cost of disconnected tools is rarely one dramatic failure. It is the daily accumulation of duplicate entry, missing context, and delayed follow-up.",
    "beforeTitle": "Fragmented operation",
    "beforeItems": [
      "Reservation details copied between tools",
      "Vehicle status confirmed through messages",
      "Agreement tasks tracked from memory",
      "Return issues discovered after the customer leaves"
    ],
    "afterTitle": "Connected operation",
    "afterItems": [
      "One reservation status visible to the team",
      "Vehicle readiness attached to the rental",
      "Pickup requirements shown before handover",
      "Return follow-up created while context is fresh"
    ]
  },
  "workflow": {
    "eyebrow": "End-to-end workflow",
    "title": "Move the rental forward without losing the thread.",
    "body": "Each step exposes the decision, owner, and next action instead of burying operations inside a generic feature list.",
    "steps": [
      ["01", "Capture the reservation", "Record dates, driver details, requirements, and source."],
      ["02", "Assign a ready vehicle", "Match availability with class, location, and readiness."],
      ["03", "Complete pickup", "Confirm documents, inspection, agreement, and handover tasks."],
      ["04", "Process the return", "Record condition, close open work, and release the vehicle."]
    ]
  },
  "roles": {
    "eyebrow": "Built for the operating team",
    "title": "Give each role the context it needs, without creating separate versions of the truth.",
    "roles": [
      ["Owner or manager", "See workload, exceptions, and operating signals across the business."],
      ["Reservations team", "Move requests from inquiry to confirmed rental with fewer handoffs."],
      [
        "Fleet and operations",
        "Know which vehicles are available, blocked, due, or awaiting action."
      ],
      ["Front desk", "Prepare pickup and return tasks before the customer is waiting."]
    ]
  },
  "modules": {
    "eyebrow": "Product modules",
    "title": "A connected core, organized around real rental work.",
    "body": "Module boundaries clarify responsibility while shared records prevent the usual copy-and-paste archaeology.",
    "items": [
      ["Reservations", "Availability, dates, customer requirements, and status in one flow."],
      ["Fleet readiness", "Vehicle availability, blocks, service state, and location context."],
      ["Rental agreements", "Pickup requirements, agreement status, and operational records."],
      [
        "Vehicle inspections",
        "Structured pickup and return condition checks with follow-up tasks."
      ],
      ["Customer records", "Rental history and contact context attached to active work."],
      [
        "Operations reporting",
        "Definitions and operational views that can be validated against source activity."
      ]
    ]
  },
  "results": {
    "eyebrow": "Measured results",
    "title": "Measure the change, not the marketing.",
    "body": "No outcome claim should appear until a real customer baseline, comparison period, and data definition are approved. The production page therefore shows the measurement plan instead of fictional percentages.",
    "metrics": [
      ["Reservation handling time", "From usable request to confirmed reservation."],
      ["Vehicle turnaround time", "From return recorded to ready-for-rental status."],
      [
        "Fleet utilization",
        "Available rental days compared with rented days, using one approved definition."
      ],
      ["Overdue follow-up", "Open overdue rentals with an assigned owner and next action."]
    ],
    "methodTitle": "Methodology required before publishing results",
    "method": [
      "Capture a pre-launch baseline using the same KPI definitions.",
      "Compare equivalent locations, fleet classes, and operating periods.",
      "Report sample size, exclusions, and measurement window.",
      "Link every public result to an approved evidence record."
    ]
  },
  "integrations": {
    "eyebrow": "Integrations",
    "title": "Connect the systems your operation already depends on.",
    "body": "Integration scope is confirmed during discovery so the proposal reflects your market, current stack, and data ownership. Named partners are not shown until connector availability is verified.",
    "items": [
      "Accounting and finance",
      "Payments and deposits",
      "Telematics and vehicle data",
      "Identity and document services",
      "Email, SMS, and notifications",
      "Website and booking channels"
    ]
  },
  "security": {
    "eyebrow": "Security and reliability",
    "title": "Evaluate the platform with evidence, not badges.",
    "body": "Certifications and service-level claims remain unpublished until approved documentation exists. During evaluation, request concrete answers for the controls that matter to your operation.",
    "checks": [
      ["Access control", "Roles, permissions, administrator actions, and offboarding."],
      ["Auditability", "Which changes are recorded, searchable, and exportable."],
      ["Data handling", "Ownership, retention, export, deletion, and subprocessors."],
      ["Continuity", "Backup, recovery, incident communication, and support process."]
    ]
  },
  "pricing": {
    "eyebrow": "Pricing preview",
    "title": "Pricing should match the operation you actually run.",
    "body": "A public price is not shown until the commercial model and included limits are approved. The evaluation starts with the factors that materially affect scope.",
    "factors": [
      "Fleet size and active locations",
      "Required modules and user roles",
      "Migration and onboarding scope",
      "Integration and support requirements"
    ],
    "primary": "Request pricing",
    "note": "No card prices, discounts, or package limits are published in this baseline."
  },
  "faq": {
    "eyebrow": "FAQ",
    "title": "Questions buyers should ask before booking a demo.",
    "items": [
      [
        "Is homePageCar only for large rental companies?",
        "The final market and packaging are still being defined. The demo should qualify fleet size, locations, workflows, and required modules rather than pretend one setup fits everyone."
      ],
      [
        "Can we keep our existing systems?",
        "Potential integrations are reviewed during discovery. Connector availability, data ownership, migration effort, and ongoing synchronization must be confirmed before they are promised."
      ],
      [
        "Does the platform support multiple languages?",
        "The website and approved design system support English, French, and Arabic. Arabic uses true document-level right-to-left behavior rather than a mirrored-looking patch."
      ],
      [
        "How is pricing calculated?",
        "The commercial model is pending approval. Until then, proposals should state the scope, included modules, limits, onboarding, integrations, and support explicitly."
      ],
      [
        "What security certifications do you have?",
        "No certification is claimed in this baseline. Security evidence should be supplied through approved documentation during evaluation and published only after verification."
      ],
      [
        "What happens during the demo?",
        "The session should map your current reservation-to-return flow, show the relevant product path, identify integration needs, and document unresolved fit questions."
      ]
    ]
  },
  "final": {
    "eyebrow": "See the full workflow",
    "title": "Bring one real rental process to the demo.",
    "body": "We will trace the handoffs, exceptions, and information your team needs from reservation through vehicle return.",
    "primary": "Book a product demo",
    "secondary": "Contact sales"
  },
  "footer": {
    "tagline": "Connected rental-car operations from reservation to return.",
    "groups": [
      [
        "Product",
        [
          ["Workflow", "#workflow"],
          ["Modules", "#modules"],
          ["Pricing", "#pricing"]
        ]
      ],
      [
        "Company",
        [
          ["Contact sales", "#contact"],
          ["Book a demo", "#demo"]
        ]
      ],
      [
        "Account",
        [
          ["Log in", "#login"],
          ["Language", "#language"],
          ["Theme", "#theme"]
        ]
      ],
      [
        "Legal",
        [
          ["Privacy", "#!"],
          ["Terms", "#!"],
          ["Accessibility", "#!"]
        ]
      ]
    ],
    "copyright": "© 2026 homePageCar. Evidence and commercial claims remain subject to approval."
  },
  "form": {
    "title": "Book a product demo",
    "body": "Tell us how your rental operation works. Required fields are marked.",
    "name": "Full name",
    "email": "Work email",
    "company": "Company",
    "fleet": "Approximate fleet size",
    "market": "Country or operating market",
    "language": "Preferred demo language",
    "message": "What should the demo focus on?",
    "submit": "Request my demo",
    "privacy": "By submitting, you agree to be contacted about this request. Privacy notice text requires legal approval.",
    "close": "Close",
    "required": "Required",
    "emailError": "Enter a valid work email address.",
    "requiredError": "This field is required.",
    "fleetOptions": [
      "Select an option",
      "1–25 vehicles",
      "26–100 vehicles",
      "101–500 vehicles",
      "More than 500 vehicles",
      "Not sure yet"
    ],
    "langOptions": ["English", "Français", "العربية"],
    "successTitle": "Demo request recorded",
    "successBody": "This prototype has completed the booking flow. No request was sent to a real sales system.",
    "submitAnother": "Submit another request",
    "submissionError": "The prototype could not complete the request. Your entries are still available. Try again.",
    "errorSummary": "Review the highlighted fields and try again."
  },
  "preview": {
    "today": "Today",
    "branch": "Central branch",
    "title": "Operations overview",
    "reservations": "Reservations",
    "ready": "Vehicles ready",
    "attention": "Needs attention",
    "active": "Active rentals",
    "r1": "Pickup at 10:30",
    "r2": "Return due at 14:00",
    "r3": "Inspection required",
    "vehicle": "Vehicle",
    "customer": "Customer",
    "status": "Status",
    "task": "Next action",
    "plate1": "ABC-2048",
    "plate2": "RNT-7712",
    "statusReady": "Ready",
    "statusDue": "Due today",
    "taskAssign": "Confirm driver documents",
    "taskInspect": "Complete return inspection"
  },
  "tour": {
    "title": "Product tour",
    "intro": "Follow one rental from reservation through return.",
    "back": "Previous",
    "next": "Next",
    "finish": "Finish tour",
    "close": "Close product tour",
    "step": "Step",
    "of": "of"
  },
  "research": {
    "title": "Research mode",
    "events": "events",
    "export": "Export events",
    "clear": "Clear",
    "close": "Close"
  }
}
