Learn / Deployment
From builder preview to your own domain.
A preview link is fine for feedback. A launch needs an address you control, a repository you own and a release you have actually tested.
Why a preview URL is not a product address
Preview URLs are tied to the tool that generated them. They can change, expire or carry the platform's branding. Anything you want people to bookmark, share or trust should live on a domain that belongs to you.
Exporting your source code
- Confirm the export contains the full application, not only a bundled build output.
- Install dependencies and run the project locally before you rely on the export.
- Record the exact commands needed to run, build and deploy it.
- Remove sample data and placeholder copy you do not intend to ship.
GitHub basics
A repository gives you history, rollback and a deployment source. Create the repository first, push the export, then connect your host to that repository rather than uploading files by hand.
Staging versus production
- Keep one environment you can break and one environment users see.
- Use separate keys and separate databases for each environment.
- Promote to production only after the staging build passes your checks.
Custom domain basics
Buy the domain in an account you own. Point it at your host by adding the DNS records your host gives you, then wait for propagation and confirm HTTPS is active before announcing the launch.
Testing before launch
- Walk the core journey end to end on a real phone, not only a resized window.
- Check slow-network behaviour and what happens when a request fails.
- Test keyboard navigation and visible focus on every interactive control.
- Confirm forms validate, submit and confirm clearly.
Branding and metadata
- Unique page title and description on every page.
- Favicon that matches your own mark.
- Share image and social metadata so links preview correctly.
- A sitemap and sensible robots rules once the content is real.
Privacy, terms and contact
If you collect an email address, you are collecting personal data. Publish a privacy policy, terms and a working contact route before you open sign-ups, and say plainly what you store and why.