# WAYLIN SPACE website

A responsive six-page static site built from the supplied screenshot direction: premium dark aerospace styling, electric-blue details, the typographic wordmark, and a geometric W mark.

## Preview locally

From this folder, run:

```sh
python3 -m http.server 4173
```

Then open `http://localhost:4173`. Any static file server can serve this folder.

## Pages

- `index.html` — Home
- `platform.html` — Waylin Orbit, Waylin Mission, Waylin Launch and Waylin Intelligence
- `technology.html` — Technology principles and development status
- `about.html` — Company and founder
- `careers.html` — Early-stage interest form, with no claimed vacancy
- `contact.html` — General enquiry form

All four modules are labelled **Planned · Under development**. Founder copy describes Tanish Gupta's aviation background and interest in aerospace without claiming space-engineering qualifications. No customers, partners, certifications, deployed products or achievements are represented.

## Contact and careers forms

Forms validate fields in the browser and build a message. By default, they do not transmit or store submissions. In the no-configuration state, the page clearly says nothing was sent and offers a copyable message.

Edit `config.js`:

```js
window.WAYLIN_CONFIG = {
  contactRecipient: "", // confirmed active contact inbox, if available
  careersRecipient: "", // confirmed active careers inbox, if available
  formEndpoint: ""     // optional HTTPS endpoint accepting JSON
};
```

With a recipient configured, submitting opens the visitor's email app as a draft; the visitor must send it. This does not confirm delivery. For direct web submissions, set `formEndpoint` to an HTTPS service you control. It must accept a JSON POST containing `name`, `email`, `subject`, `message`, and `form`, allow the deployed site origin via CORS, and return a 2xx response when it has accepted the submission. Configure spam protection and retention rules at that service. Do not put private API keys in this public file.

Do not set `info@waylin.space` or `careers@waylin.space` until those inboxes are confirmed active.

## Deploy and connect waylin.space

1. Choose a static hosting provider such as Cloudflare Pages, Netlify, Vercel, or GitHub Pages.
2. Upload this folder or connect the repository containing it. Set the publish/output directory to `outputs/waylin-space-site`; there is no build command.
3. Preview the provider's generated URL and confirm all six `.html` pages load.
4. In the hosting dashboard, add `waylin.space` and `www.waylin.space` as custom domains. Follow the provider's current DNS instructions exactly.
5. At the domain registrar's DNS panel, add the provider-specified records for the apex (`@`) and `www`. Remove conflicting old website records only after you have recorded them and confirmed the new target. DNS values vary by host, so use the values shown in the selected provider's dashboard.
6. Set the provider's preferred canonical domain (apex or `www`) and redirect the other hostname to it. Wait for DNS and HTTPS certificate provisioning, then check both hostnames and each page on desktop and mobile.
7. Configure `config.js` only after the inboxes or form endpoint are ready. Submit test enquiries through the deployed site and verify receipt at the destination before describing the forms as delivering messages.

The site has not been published and the domain has not been connected by this local build.

## Brand assets

The supplied logo appears inside the screenshots rather than as a standalone export. The site includes a vector approximation: the horizontal wordmark is typeset in the Michroma font and the structural W is drawn as SVG. Replace `assets/logo.svg` and `assets/waylin-mark.svg` with approved exported artwork when available. `assets/favicon.svg` is the W mark on navy.

The hero and feature photography load from Unsplash URLs and therefore need an internet connection. For production, confirm image licensing and consider self-hosting approved images.