Public landing for the Techton ecosystem
Design precise CAD automation workflows with Techton
Understand the product structure that links AutoLISP Toolkit, Cader, and Timerit in one view, while the current entry point stays focused on brand introduction and authentication.
Landing-first approach
The homepage explains brand structure before deeper product flows.
Shared UI first
Reusable primitives are consumed from `@techton7/svelte-components` first.
Product surfaces stay separate
`/auth` and future dashboards keep a clearer product-focused visual tone.
System matrix
Keep the homepage expressive and the product surfaces focused
The landing page owns the brand story and information architecture, while actual usage flows continue into `/auth` and later product screens.
SHARED UI
svelte-components
Manage reusable primitives and wrappers in the shared package first
AUTH SURFACE
/auth
Keep sign-in and registration inside a product-oriented flow
HOME FOCUS
public landing
Condense service framing, structure, and CTA into one page
Ecosystem
A landing page that frames the Techton service ecosystem
At this stage, the homepage focuses less on exhaustive feature detail and more on making the product axes and expansion paths easy to understand.
An editor-centered toolkit that helps AutoLISP development workflows move faster.
It highlights syntax support, assisted input, and repeatable automation-oriented flows.
Until detailed service pages exist, the landing page introduces only the core role of the product.
A product axis that connects desktop CAD experience with automation macro management.
It gives the landing page a clear bridge toward the Tauri-based product direction.
The homepage can be more brand-heavy while the real product UI remains restrained and focused.
A mobile-centered product axis for time tracking and reminder-driven workflow support.
It explains how productivity signals can join the broader Techton structure.
For now, it mainly helps communicate service connectivity and future expansion.
Why Techton
Three implementation principles for the current homepage
Instead of copying the Stitch reference literally, this homepage adapts it to the real project structure and shared UI policy.
The first screen should strongly communicate the CAD automation platform identity, while deeper flows move into dedicated product views.
Buttons, cards, dialogs, and similar primitives should be consumed through `@techton7/svelte-components` first.
The landing page avoids fake destinations and limits entry points to `/auth` and page anchors for now.
Ready to start
Begin with the homepage, then move into real product flows
The public landing page gives visitors the product map first, then gradually hands off to `/auth` and later product surfaces.
Next implementation
- • Keep homepage-specific composition local to the app
- • Add missing shared primitives in the shared package first
- • Continue refining auth screens as product UI, not marketing UI