Use the self-hosted path with GitHub

How to use this

1. 1Finish and refresh the private website you want to hand off.
2. 2Choose a paid publishing plan; free accounts can create and improve private websites but cannot publish or export a self-hosted release.
3. 3Open Account, then Profile, expand Advanced setup, and choose Self-hosted path.
4. 4Select the website and connect GitHub. GitHub asks you to approve private-repository access.
5. 5Choose Send website code to GitHub. DriftLess creates a private repository for that website or updates its existing repository.
6. 6Open the repository and give it to your developer, or connect it to the static hosting provider you manage.
7. 7Repeat the export whenever you want the repository to receive a newer reviewed version.

Keep in mind

• You do not need GitHub for the normal DriftLess path. Answering simple questions, reviewing, editing, and publishing with DriftLess require no technical skills.
• Sending files to GitHub does not put them online. The repository owner remains responsible for external hosting, deployments, domains, security headers, and future maintenance.
• The export contains the finished static website, not DriftLess editing controls or server-side selling and payment infrastructure. Websites with DriftLess checkout must use DriftLess publishing and cannot use the self-hosted export in V1.