Company infrastructure
Tara Systems website
An early-stage company with no customer base still needs a public presence it can stand behind. This website is the first working artifact of that need: it explains what Tara Systems does, makes the working process legible, and gives prospective clients and collaborators a direct path to start a conversation.
The need
The company must establish trust without testimonials, client logos, or usage statistics, and without claiming more maturity or scale than it has. The website therefore has to demonstrate capability through structure, substance, and honesty rather than social proof.
Constraints and considerations
The site must be inexpensive to run, contain no fabricated content, remain easy to extend as real portfolio and product entries exist, and never let a placeholder reach production unnoticed.
Approach
A prerendered SvelteKit application with TypeScript throughout. Content lives in typed data modules rather than a CMS, so every portfolio and product entry is validated at build time and cannot render publicly until it is explicitly published. The contact form delivers email through a server action configured by environment variables and reports missing configuration honestly instead of discarding submissions.
Design and engineering decisions
The implementation deliberately applies the company philosophy to itself: small dependency surface, no database, no CMS, content as data, and restrained editorial design built on a token system.
Recognizably documented decisions include:
- Prerendered marketing pages; only the contact route runs on the server
- Content as typed TypeScript modules with a publication gate
- Hand-written CSS design tokens instead of a styling framework
- Self-hosted variable fonts to avoid third-party requests
- Email delivery via a single fetch-based module that fails explicitly
Implementation
The public site is a SvelteKit 3 application with strict TypeScript. Every page carries unique metadata and a canonical URL; sitemap and robots.txt are generated from the same site configuration. Accessibility targets WCAG 2.2 AA: semantic landmarks, keyboard-operable navigation, labeled form controls, and reduced-motion support.
Known limitations
- The portfolio intentionally contains only work that can be described truthfully; it grows as real projects exist.
- Inquiry email delivery is not yet configured and the form reports that fact until it is.
- Legal pages await review for the applicable jurisdictions.
Next steps
- Publish further project and product entries as they reach a describable state
- Configure the production domain and inquiry delivery (see docs/launch.md)