Skip to content

hosting: prepare the commercial front door independently of GitHub Pages #4

Open

Description

@turinglambdaai

Problem and decision

The site is becoming a product-family commercial front door. GitHub Pages limits exclude using Pages primarily for online business/commercial transactions or commercial SaaS. Existing project/documentation pages and a future paid-product journey are different uses; do not assume that free static hosting automatically fits the latter.

Prepare a static deployment on an appropriate commercial-hosting service, such as Cloudflare Pages or the reviewed web host. Preserve the existing static architecture, custom domain, self-hosted fonts, URLs and complete English/Chinese text. No page redesign or site-framework rewrite is needed.

Safe migration handoff

  1. Inventory current DNS, authoritative registrar, custom domains, email records, deployed commit and rollback values without publishing private account data.
  2. Build an isolated preview from a pinned source and verify all product links, languages, fonts, dark mode, mobile/focus, redirects and cache rules. Test mainland and overseas access; ordinary Cloudflare global service does not establish mainland CDN coverage.
  3. Keep internal portfolio/pricing/architecture plans outside customer navigation. Actual public offers belong to product sites after readiness.
  4. Put checkout/webhooks/claims and hosted product APIs on their reviewed service origins; keep secrets and account sessions out of static repositories.
  5. Review applicable filing/hosting and merchant-domain requirements for the actual operators/origins.
  6. Switch DNS only as a separate planned deployment, verify the actual HTTPS result, then retain or restore the previous routing if it fails. Do not change MX/TXT or nameservers incidentally.

Architecture handoff only: no Cloudflare project, DNS, purchase, account or live site migration was performed by creating this issue.

Related existing homepage entry: #2. This hosting slice is independent of page redesign and does not move maintainer plans back into customer navigation.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions