theupdateframework / theupdateframework/theupdateframework.io
Make the specification available under https://theupdateframework.io rather than GH pages
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 25
- Forks
- 46
- PR merge metrics
- No merged PRs in 30d
Description
We can host the specification on Netlify using the current build process, and then config DNS to make the spec (versions) available via, say, spec.theupdateframework.io, with a rewrite to https://theupdateframework.io/spec/:splat.
We could then setup analytics over the spec too.
WDYT @JustinCappos?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the current build process and how the specification versions are published. Determine how Netlify, DNS for spec.theupdateframework.io, and the proposed rewrite to the main site fit together; done means the specification is reachable at the new URL, with analytics considered for the hosted spec.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- html
- Domain
- devops, documentation
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100