Troyen Website — Project Description

Document set version: 0.1.0

Date: 2026-09-05

Status: Initial project scaffold created; the new site has not yet replaced the current public website.

Purpose

Troyen Website is the public-facing website for Troyen Data. It explains the structured, time-sensitive racing-data service, introduces its API integration model, presents coverage and subscription information, answers common questions, and lets prospective customers request API access.

Audience

• Software teams integrating racing data into applications, analytics pipelines, and operational systems.
• Prospective customers assessing coverage, update timing, subscription options, and API access.
• Existing customers looking for basic support and subscription or billing guidance.

Initial Scope

The replacement site will build on the verified content and workflows of:

• https://tdatasite.com/
• https://tdatasite.com/Home/FAQPage

The established public experience includes:

• Troyen Data service and coverage overview.
• RESTful API and JSON integration information.
• Subscription and pricing-enquiry information.
• API-key enquiry form.
• FAQ content covering credentials, rate limits, regions, refresh timing, subscriptions, and billing.

Technical Direction

The new local project uses a React and TypeScript site scaffold powered by Vinext, Vite, Tailwind CSS, and the supplied Shadcn component set. The project is intended to be maintained at:

C:\Users\Robert\Projects\Troyen\TroyenWebSite

Source repository:

https://github.com/QuantumDataGroup/TroyenWebSite.git

The source repository was empty when the project was initialized.

Known Integration Behaviour

The current public site submits API-key requests to /api/Auth/getApiToken. The replacement site's final backend and deployment integration have not yet been confirmed and must be verified before reproducing production form submission.

Branding

Use Troyen Data as the working brand name. The current FAQ contains inconsistent instances of “Troyan Data”; these should not be carried forward without an explicit branding decision.

Constraints and Open Work

• Preserve accurate public content while improving the site incrementally.
• Do not expose credentials, private API details, or production data.
• Confirm the production form endpoint and deployment target before launch.
• Confirm the final information architecture, visual direction, and content changes before replacing the live site.