Skip to content

lynbtc/LYN

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

183 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

LYN.

is a tool to build. an operating layer.
code by vibe. free open source everything. bitcoin.

currently: premium modular sauna system.
design - morten bo jensen / groundwork studio.
manufacturing - koerner saunabau / est. 1949.

What This Repo Is

Live production website for lyn.page and related subdomains.
Pure static stack: HTML, CSS, JS. No framework. No build step.

Local Development

Run from repo root:

npx serve .

The command will print the actual local URL (usually http://localhost:3000). Note that npx serve does not respect the Netlify _redirects file — pretty paths like /thermal-logic or /documents will only work on the deployed site. For local testing use the raw filename.html URLs.

Deployment

Pushes to main auto-deploy to Netlify.
Treat every main push as production.

Site map

  • Files are the inventory. Each surface is a root-level *.html (or archive/*.html for dormant or superseded work). There is no build step, so the tree is authoritative.
  • URLs and hosts live in _redirects. Pretty paths (/documents, /spa, …), subdomain roots, and legacy redirects are all defined there. When you add or move a public page, update _redirects as needed; this README does not duplicate that matrix.
  • Rough groupings: LYN home and text-forward tools (documents, onepager, collaborate, lynai, …), SAUNA / editorial product pages (sauna, productsheet, spa, residence, press, …), deeper tools (e.g. siteplanning), and archived pitches under archive/.

Archived pages

archive/ holds legacy decks, pitches, and PDF sources. Old apex URLs that still get traffic are handled with redirects in _redirects.

Subdomains

Which host serves which HTML file is defined in _redirects (e.g. sauna, koerner, siteplanning subdomains). Read that file when wiring a new subdomain or path.

Editing Guardrails

  • Keep diffs minimal and intentional
  • Stay in plain HTML/CSS/JS
  • Verify UI changes visually before shipping
  • Avoid adding dependencies unless absolutely required
  • No public pricing on general public product pages

Contact

About

website

Resources

License

Stars

Watchers

Forks

Contributors