From 515e3f9ace94e7a593e6bea02477bbc7c300c543 Mon Sep 17 00:00:00 2001 From: Carbon Alabel Date: Mon, 11 Jun 2018 19:49:00 +0200 Subject: [PATCH] Update links Some of them were broken, the others just involved an unnecessary redirect. --- .github/ISSUE_TEMPLATE/inconsistency.md | 4 ++-- .github/issue_template.md | 2 +- README.md | 6 +++--- docs/CREST_to_ESI.md | 2 +- docs/FAQ.md | 6 +++--- docs/XML_to_ESI.md | 2 +- docs/esi_introduction.md | 2 +- docs/warning_header.md | 2 +- 8 files changed, 13 insertions(+), 13 deletions(-) diff --git a/.github/ISSUE_TEMPLATE/inconsistency.md b/.github/ISSUE_TEMPLATE/inconsistency.md index 8d2d973..644a956 100644 --- a/.github/ISSUE_TEMPLATE/inconsistency.md +++ b/.github/ISSUE_TEMPLATE/inconsistency.md @@ -31,5 +31,5 @@ Check all boxes that apply to this issue: - [ ] Inconsistency description is provided - [ ] Inconsistent route(s) are provided -- [ ] Resolution [will require a version bump](https://esi.github.io/esi-issues/breaking_changes) -- [ ] Resolution [does not require a version bump](https://esi.github.io/esi-issues/breaking_changes) +- [ ] Resolution [will require a version bump](https://docs.esi.evetech.net/docs/breaking_changes) +- [ ] Resolution [does not require a version bump](https://docs.esi.evetech.net/docs/breaking_changes) diff --git a/.github/issue_template.md b/.github/issue_template.md index 9f45b81..8c91618 100644 --- a/.github/issue_template.md +++ b/.github/issue_template.md @@ -1,5 +1,5 @@ # Stop -You're doing it wrong. Go back to the [README.md](https://esi.github.io/esi-issues/) and click on one of the "Opening a new issue" links to start with an appropriate issue template. +You're doing it wrong. Go to [Opening a new issue](https://docs.esi.evetech.net/#opening-a-new-issue) and click on one of the links to start with an appropriate issue template. Issues submitted without a template are likely to be rejected and closed immediately. diff --git a/README.md b/README.md index 4b0a0a7..35c542d 100644 --- a/README.md +++ b/README.md @@ -18,7 +18,7 @@ ESI is a constant work in progress. Here is a list of sources you can use to kee - Follow [@TeamTechCo](https://twitter.com/TeamTechCo), as well as [@CCP_SnowedIn](https://twitter.com/CCP_SnowedIn) and [@CCP_Zoetrope](https://twitter.com/CCP_Zoetrope) on Twitter. - Join the [`#esi` channel on Tweetfleet Slack](https://tweetfleet.slack.com/messages/C30KX8UUX/). You can get an invite [here](https://www.fuzzwork.co.uk/tweetfleet-slack-invites/). - Read the posts on the [Third Party Developer Blog](https://developers.eveonline.com/blog). -- Follow the activity in this repository, particularly the [ESI changelog](changelog.md) and [issues that are in progress](https://github.com/esi/esi-issues/issues?q=label%3A%22In+Progress%22). +- Follow the activity in this repository, particularly the [ESI changelog](changelog.md) and [issues that are in progress](https://github.com/esi/esi-issues/labels/in-progress). ## Opening a new issue @@ -56,9 +56,9 @@ Examples: ## Migration Guide -### [CREST -> ESI](https://esi.github.io/esi-issues/docs/CREST_to_ESI) +### [CREST -> ESI](https://docs.esi.evetech.net/docs/CREST_to_ESI) -### [XML -> ESI](https://esi.github.io/esi-issues/docs/XML_to_ESI) +### [XML -> ESI](https://docs.esi.evetech.net/docs/XML_to_ESI) ## Issue velocity diff --git a/docs/CREST_to_ESI.md b/docs/CREST_to_ESI.md index 911adc0..854e23a 100644 --- a/docs/CREST_to_ESI.md +++ b/docs/CREST_to_ESI.md @@ -4,7 +4,7 @@ title: CREST to ESI Migration # CREST to ESI Migration -See also [XML to ESI Migration](https://esi.github.io/esi-issues/XML_to_ESI) +See also [XML to ESI Migration](https://docs.esi.evetech.net/docs/XML_to_ESI) # Table of Contents diff --git a/docs/FAQ.md b/docs/FAQ.md index d2f4fac..b593c46 100644 --- a/docs/FAQ.md +++ b/docs/FAQ.md @@ -16,11 +16,11 @@ They embed the version in the path, resulting in more stable clients. [Please re ### What constitutes a version increase? -[Please refer to the breaking changes document](https://esi.github.io/esi-issues/docs/breaking_changes). +[Please refer to the breaking changes document](https://docs.esi.evetech.net/docs/breaking_changes). ### Where can I see upcoming changes? -[You can use ESI's diff interface](https://esi.evetech.net/diff/latest/dev/) for the exact differences per route. There is also the [ESI changelog](https://esi.github.io/esi-issues/changelog) for historical reference and to know when upcoming changes will be promoted. +[You can use ESI's diff interface](https://esi.evetech.net/diff/latest/dev/) for the exact differences per route. There is also the [ESI changelog](https://docs.esi.evetech.net/changelog) for historical reference and to know when upcoming changes will be promoted. ### Is there an ESI client library in <language_x>? @@ -28,7 +28,7 @@ Probably. Check the [awesome-eve](https://github.com/devfleet/awesome-eve) repos ### What happened to CREST and XML API? -After [18 months of notice](https://www.eveonline.com/article/introducing-esi/) both CREST and XML API were [shut down on May 8th, 2018](https://developers.eveonline.com/blog/article/a-eulogy-for-xml-crest). Please see either the [CREST to ESI](https://esi.github.io/esi-issues/docs/CREST_to_ESI) or [XML to ESI](https://esi.github.io/esi-issues/docs/XML_to_ESI) migration guides for assistance in porting your old applications to ESI. +After [18 months of notice](https://www.eveonline.com/article/introducing-esi/) both CREST and XML API were [shut down on May 8th, 2018](https://developers.eveonline.com/blog/article/a-eulogy-for-xml-crest). Please see either the [CREST to ESI](https://docs.esi.evetech.net/docs/CREST_to_ESI) or [XML to ESI](https://docs.esi.evetech.net/docs/XML_to_ESI) migration guides for assistance in porting your old applications to ESI. ## Further Questions? diff --git a/docs/XML_to_ESI.md b/docs/XML_to_ESI.md index 97a78f2..0546753 100644 --- a/docs/XML_to_ESI.md +++ b/docs/XML_to_ESI.md @@ -4,7 +4,7 @@ title: XML to ESI Migration # XML to ESI Migration -See also [CREST to ESI Migration](https://esi.github.io/esi-issues/CREST_to_ESI) +See also [CREST to ESI Migration](https://docs.esi.evetech.net/docs/CREST_to_ESI) # Table of Contents diff --git a/docs/esi_introduction.md b/docs/esi_introduction.md index 33f2268..11dbdb4 100644 --- a/docs/esi_introduction.md +++ b/docs/esi_introduction.md @@ -1,7 +1,7 @@ # ESI (EVE Swagger Interface) The ESI API is the official RESTful API for EVE third party development. It leverages [Swagger](https://swagger.io/) so that documentation about the API is always up to date and not dependent on documentation websites like this one. You can find all the endpoints -and try them out at [https://esi.evetech.net/latest/](https://esi.evetech.net/latest/). +and try them out at [https://esi.evetech.net/ui/](https://esi.evetech.net/ui/). ## Fundamentals ### Multi-tenant to the core diff --git a/docs/warning_header.md b/docs/warning_header.md index 7369d26..f3e9f9a 100644 --- a/docs/warning_header.md +++ b/docs/warning_header.md @@ -10,7 +10,7 @@ Warnings that start with `299` are there to inform you the route you just reques ## `199` -Instead of unhappy users, look for `199` warnings ahead of time. These exist in order to tell you the route you have just requested has an update available. This means it's probably a good time to [check the changelog](https://esi.github.io/esi-issues/changelog.html) to see when this new upgrade will be promoted to latest, and/or update your application to take advantage of the new features the change brings. +Instead of unhappy users, look for `199` warnings ahead of time. These exist in order to tell you the route you have just requested has an update available. This means it's probably a good time to [check the changelog](https://docs.esi.evetech.net/changelog) to see when this new upgrade will be promoted to latest, and/or update your application to take advantage of the new features the change brings. The typical `199` warning is: `199 - This route has an upgrade available.` You can use the diff page to view the exact details of the upcoming changes. The [v3 ESI webui](https://esi.evetech.net/ui/) will have links in the description to the diff page for any routes with updates available.