Keep extensions.oriz.in catalog AS WELL AS per-extension subdomains

Central catalog + per-extension subdomains

Keep extensions.oriz.in catalog AS WELL AS per-extension subdomains

Decision

The extensions.oriz.in catalog is NOT being collapsed in favor of per-extension subdomains. Both exist: the catalog is the family-wide “browse all extensions” surface, and each <slug>.oriz.in is the deep marketing/docs site for one extension. They cross-link.

Why

Per-extension subdomains optimise for SEO and store-review compliance on a single product. The catalog optimises for users who want to see the family’s full extension portfolio in one view — a different intent. Killing the catalog would lose the cross-discovery surface and the apex AdSense placement opportunity; killing per-extension subdomains would lose store-friendly privacy URLs and per-product SEO. Both are cheap on Cloudflare Pages free, so we keep both.

Implications

• extensions.oriz.in lists every extension with name, one-line pitch, install buttons, and a “learn more” link to <slug>.oriz.in.
• Each <slug>.oriz.in site links back to the catalog in its footer.
• The catalog is also embedded as a section at oriz.in/extensions for cross-promo (see oriz-home-cross-promos-extensions).
• Catalog data is generated from the extensions/ submodules’ manifests at build time — single source of truth, no drift between the catalog and per-extension sites.
• AdSense apex application covers all of these per AdSense 2026 rules.

Cross-refs

• Per-extension subdomain
• Big website per extension
• oriz-home cross-promos extensions
• AdSense apex application

Edit on GitHub · Back to index