OAI / OAI/spec.openapis.org

Consider alternatives to GitHub Pages

Open
#31 6 comments 0 reactions 1 assignee View on GitHub

@pavelkornev is already working on this.

Since Feb 12, 2026.

Housekeeping
Dominant language
HTML
Stars
12
Forks
18
Avg merge
7h 31m
Merged PRs (30d)
4

Description

GitHub Pages has several very problematic limitations for a project focused on HTTP standards:

  • It does not allow setting Content-Type except via file extension, which is not how our schemas work
  • It does not support HTTP redirects, only HTML-driven refresh-redirects

The first two are essential for us, as we want to have our JSON Schemas served as JSON, and we want to have a latest resource that uses redirects instead of serving a schema with a mismatched $id (this helps prevent people from thinking that the latest URI can be used in $refs, etc.).

Netlify seems to be the most popular suggestion on our Slack, with @jmertic having seen it used for similar purposes and at least one other person recommending it. I've also seen Cloudflare Pages used. Both can run from GitHub repos, and I'm pretty sure both can solve both of our main problems. The distinction might be which has the most services available through any sort of open source foundation-oriented plan (I believe both have or at least once had such plans), which I have not investigated at all.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.