-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Charter next #122
Charter next #122
Conversation
Undated version to use for charter development purposes.
To Be Defined later in the chartering process.
I added Netlify to make it easier to review the rendered HTML of pull requests. |
@xfq thanks, does Netlify provide diff similar to pr-preview? Netlify docs did not mention. And while we’re here, can we rename the repo to das-charter without breaking links? |
No. We can use PR Preview to provide a diff. Although it can also provide previews, it has been unstable recently and only supports previews of a single document in a repo. |
I'll look into it. |
✅ Deploy Preview for w3c-das-charter ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
GitHub automatically redirect references to the issues/PRs from the old name to the new one, but not GitHub Pages, so I created a I don't have a good solution at the moment, but in order to avoid this kind of problem in the future, one approach I think of is to use Netlify (https://w3c-das-charter.netlify.app/DASCharter-2021.html) (or Vercel etc.) instead of GitHub Pages (https://w3c.github.io/das-charter/DASCharter-2021.html) for the rendered HTML. Since Netlify is not strongly coupled to a GitHub repo, we can configure the redirects ourselves. |
@xfq here’s an example of a solution that works without breaking any links: https://github.com/webscreens/webscreens.github.io/blob/master/window-placement/index.html |
Great idea! Filed w3c/w3c.github.io#108 |
Superseded by #126 |
No description provided.