melabidi/Rental-operations-platform
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

chore: fix prettier formatting, regenerate phase9 manifest, add missing config files (.env.example, .node-version, .nvmrc, CI workflow)
CI / test (push) Failing after 28s
Details

Browse Source
This commit is contained in:
root
2026-06-25 20:12:15 -04:00
parent c43620a005
commit b7a640735c
36 changed files with 3402 additions and 1857 deletions
Download Patch File Download Diff File Expand all files Collapse all files
contracts/phase9/localization/locales/en/homepage.json
+39 -161
View File
@@ -7,26 +7,11 @@
},
"header": {
"nav": [
[
"product",
"Product"
],
[
"workflow",
"Workflow"
],
[
"modules",
"Modules"
],
[
"pricing",
"Pricing"
],
[
"faq",
"FAQ"
]
["product", "Product"],
["workflow", "Workflow"],
["modules", "Modules"],
["pricing", "Pricing"],
["faq", "FAQ"]
],
"login": "Log in",
"demo": "Book a demo",
@@ -50,22 +35,10 @@
"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."
]
["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": {
@@ -92,48 +65,23 @@
"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."
]
["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."
],
["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."
]
["Front desk", "Prepare pickup and return tasks before the customer is waiting."]
]
},
"modules": {
@@ -141,26 +89,14 @@
"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."
],
["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."
],
["Customer records", "Rental history and contact context attached to active work."],
[
"Operations reporting",
"Definitions and operational views that can be validated against source activity."
@@ -172,22 +108,13 @@
"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."
],
["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."
]
["Overdue follow-up", "Open overdue rentals with an assigned owner and next action."]
],
"methodTitle": "Methodology required before publishing results",
"method": [
@@ -215,22 +142,10 @@
"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."
]
["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": {
@@ -289,65 +204,32 @@
[
"Product",
[
[
"Workflow",
"#workflow"
],
[
"Modules",
"#modules"
],
[
"Pricing",
"#pricing"
]
["Workflow", "#workflow"],
["Modules", "#modules"],
["Pricing", "#pricing"]
]
],
[
"Company",
[
[
"Contact sales",
"#contact"
],
[
"Book a demo",
"#demo"
]
["Contact sales", "#contact"],
["Book a demo", "#demo"]
]
],
[
"Account",
[
[
"Log in",
"#login"
],
[
"Language",
"#language"
],
[
"Theme",
"#theme"
]
["Log in", "#login"],
["Language", "#language"],
["Theme", "#theme"]
]
],
[
"Legal",
[
[
"Privacy",
"#!"
],
[
"Terms",
"#!"
],
[
"Accessibility",
"#!"
]
["Privacy", "#!"],
["Terms", "#!"],
["Accessibility", "#!"]
]
]
],
@@ -377,11 +259,7 @@
"More than 500 vehicles",
"Not sure yet"
],
"langOptions": [
"English",
"Français",
"العربية"
],
"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",