Make the specification available under https://theupdateframework.io rather than GH pages

Open
#90 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
30/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
html
Domain
devops, documentation

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.

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?

Dominant language
HTML
Stars
25
Forks
46
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

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.

More from theupdateframework/theupdateframework.io

All issues in theupdateframework/theupdateframework.io

Similar issues

More DevOps issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.