type: rule
status: active
timestamp: 2026-06-23
tags: [rule, hosting, cloudflare-pages, github-pages, apps, scope]

Cloudflare Pages = apps only. Everything else = GitHub Pages

CF Pages for apps, GH Pages for everything else

CF Pages = apps only. Everything else = GitHub Pages

Rule

A submodule gets a CF Pages project if and only if it lives under repos/oriz/own/prod/apps/. Everything else — npm packages, APIs, books, extensions, skills, forks, data repos — hosts on GitHub Pages instead. Stale CF Pages projects for non-apps must be deleted.

The 25 apps that get CF Pages projects

hub (2)

personal (1)

content (8)

tools (15)

Total: 26 CF Pages projects (with www.oriz.in sharing the oriz-app project).

What does NOT get a CF Pages project

For each of these, if a public landing page is desired, host on GH Pages and add a “for more information visit oriz.in” link.

Why

  1. CF Pages 100-project soft cap — staying under it. With 26 apps + 5-10 unrelated projects we have ~30, plenty of headroom.
  2. GH Pages for static JSON is correct — APIs already serve JSON from chirag127.github.io, no Worker/Pages indirection adds value.
  3. CF Pages auto-deploy needs OAuth handshake — every new CF Pages project requires interactive GitHub authorization once. Limiting to 26 apps means 26 one-time clicks, not 80.
  4. Mental model: if it’s a Pro/Max app you’d monetize, it’s on CF Pages. If it’s a public catalog/JSON/docs, it’s on GH Pages.

Implementation

Delete from CF Pages dashboard any project that isn’t on the 26 list above. Specifically remove (from prior audit):

Cross-refs


Edit on GitHub · Back to index