💫 Update website (#3285)
<!--- Provide a general summary of your changes in the title. -->
## Description
The new website is implemented using [Gatsby](https://www.gatsbyjs.org) with [Remark](https://github.com/remarkjs/remark) and [MDX](https://mdxjs.com/). This allows authoring content in **straightforward Markdown** without the usual limitations. Standard elements can be overwritten with powerful [React](http://reactjs.org/) components and wherever Markdown syntax isn't enough, JSX components can be used. Hopefully, this update will also make it much easier to contribute to the docs. Once this PR is merged, I'll implement auto-deployment via [Netlify](https://netlify.com) on a specific branch (to avoid building the website on every PR). There's a bunch of other cool stuff that the new setup will allow us to do – including writing front-end tests, service workers, offline support, implementing a search and so on.
This PR also includes various new docs pages and content.
Resolves #3270. Resolves #3222. Resolves #2947. Resolves #2837.
### Types of change
enhancement
## Checklist
<!--- Before you submit the PR, go over this checklist and make sure you can
tick off all the boxes. [] -> [x] -->
- [x] I have submitted the spaCy Contributor Agreement.
- [x] I ran the tests, and all new and existing tests passed.
- [x] My changes don't require a change to the documentation, or if they do, I've added all required information.
2019-02-17 18:31:19 +00:00
|
|
|
redirects = [
|
2019-02-20 13:33:32 +00:00
|
|
|
# Netlify
|
2019-03-19 13:49:35 +00:00
|
|
|
{from = "https://spacy.netlify.com/*", to="https://spacy.io/:splat", force = true },
|
2020-07-01 11:23:58 +00:00
|
|
|
# Subdomain for branches
|
2020-07-01 19:33:20 +00:00
|
|
|
{from = "https://nightly.spacy.io/*", to="https://nightly-spacy-io.spacy.io/:splat", force = true, status = 200},
|
2020-10-15 10:42:30 +00:00
|
|
|
# TODO: update this with the v2 branch build once v3 is live (status = 200)
|
|
|
|
|
{from = "https://v2.spacy.io/*", to="https://spacy.io/:splat", force = true},
|
2019-02-24 12:37:50 +00:00
|
|
|
# Old subdomains
|
|
|
|
|
{from = "https://survey.spacy.io/*", to = "https://spacy.io", force = true},
|
|
|
|
|
{from = "http://survey.spacy.io/*", to = "https://spacy.io", force = true},
|
|
|
|
|
{from = "https://alpha.spacy.io/*", to = "https://spacy.io", force = true},
|
|
|
|
|
{from = "http://alpha.spacy.io/*", to = "https://spacy.io", force = true},
|
💫 Update website (#3285)
<!--- Provide a general summary of your changes in the title. -->
## Description
The new website is implemented using [Gatsby](https://www.gatsbyjs.org) with [Remark](https://github.com/remarkjs/remark) and [MDX](https://mdxjs.com/). This allows authoring content in **straightforward Markdown** without the usual limitations. Standard elements can be overwritten with powerful [React](http://reactjs.org/) components and wherever Markdown syntax isn't enough, JSX components can be used. Hopefully, this update will also make it much easier to contribute to the docs. Once this PR is merged, I'll implement auto-deployment via [Netlify](https://netlify.com) on a specific branch (to avoid building the website on every PR). There's a bunch of other cool stuff that the new setup will allow us to do – including writing front-end tests, service workers, offline support, implementing a search and so on.
This PR also includes various new docs pages and content.
Resolves #3270. Resolves #3222. Resolves #2947. Resolves #2837.
### Types of change
enhancement
## Checklist
<!--- Before you submit the PR, go over this checklist and make sure you can
tick off all the boxes. [] -> [x] -->
- [x] I have submitted the spaCy Contributor Agreement.
- [x] I ran the tests, and all new and existing tests passed.
- [x] My changes don't require a change to the documentation, or if they do, I've added all required information.
2019-02-17 18:31:19 +00:00
|
|
|
# Old demos
|
2020-04-16 12:45:25 +00:00
|
|
|
{from = "/demos/*", to = "https://explosion.ai/demos/:splat", force = true},
|
💫 Update website (#3285)
<!--- Provide a general summary of your changes in the title. -->
## Description
The new website is implemented using [Gatsby](https://www.gatsbyjs.org) with [Remark](https://github.com/remarkjs/remark) and [MDX](https://mdxjs.com/). This allows authoring content in **straightforward Markdown** without the usual limitations. Standard elements can be overwritten with powerful [React](http://reactjs.org/) components and wherever Markdown syntax isn't enough, JSX components can be used. Hopefully, this update will also make it much easier to contribute to the docs. Once this PR is merged, I'll implement auto-deployment via [Netlify](https://netlify.com) on a specific branch (to avoid building the website on every PR). There's a bunch of other cool stuff that the new setup will allow us to do – including writing front-end tests, service workers, offline support, implementing a search and so on.
This PR also includes various new docs pages and content.
Resolves #3270. Resolves #3222. Resolves #2947. Resolves #2837.
### Types of change
enhancement
## Checklist
<!--- Before you submit the PR, go over this checklist and make sure you can
tick off all the boxes. [] -> [x] -->
- [x] I have submitted the spaCy Contributor Agreement.
- [x] I ran the tests, and all new and existing tests passed.
- [x] My changes don't require a change to the documentation, or if they do, I've added all required information.
2019-02-17 18:31:19 +00:00
|
|
|
# Old blog
|
2020-04-16 12:45:25 +00:00
|
|
|
{from = "/blog/*", to = "https://explosion.ai/blog/:splat", force = true},
|
|
|
|
|
{from = "/feed", to = "https://explosion.ai/feed", force = true},
|
|
|
|
|
{from = "/feed.xml", to = "https://explosion.ai/feed", force = true},
|
💫 Update website (#3285)
<!--- Provide a general summary of your changes in the title. -->
## Description
The new website is implemented using [Gatsby](https://www.gatsbyjs.org) with [Remark](https://github.com/remarkjs/remark) and [MDX](https://mdxjs.com/). This allows authoring content in **straightforward Markdown** without the usual limitations. Standard elements can be overwritten with powerful [React](http://reactjs.org/) components and wherever Markdown syntax isn't enough, JSX components can be used. Hopefully, this update will also make it much easier to contribute to the docs. Once this PR is merged, I'll implement auto-deployment via [Netlify](https://netlify.com) on a specific branch (to avoid building the website on every PR). There's a bunch of other cool stuff that the new setup will allow us to do – including writing front-end tests, service workers, offline support, implementing a search and so on.
This PR also includes various new docs pages and content.
Resolves #3270. Resolves #3222. Resolves #2947. Resolves #2837.
### Types of change
enhancement
## Checklist
<!--- Before you submit the PR, go over this checklist and make sure you can
tick off all the boxes. [] -> [x] -->
- [x] I have submitted the spaCy Contributor Agreement.
- [x] I ran the tests, and all new and existing tests passed.
- [x] My changes don't require a change to the documentation, or if they do, I've added all required information.
2019-02-17 18:31:19 +00:00
|
|
|
# Old documentation pages (1.x)
|
2020-04-16 12:45:25 +00:00
|
|
|
{from = "/docs/usage/processing-text", to = "/usage/linguistic-features", force = true},
|
|
|
|
|
{from = "/docs/usage/deep-learning", to = "/usage/training", force = true},
|
|
|
|
|
{from = "/docs/usage/pos-tagging", to = "/usage/linguistic-features#pos-tagging", force = true},
|
|
|
|
|
{from = "/docs/usage/dependency-parse", to = "/usage/linguistic-features#dependency-parse", force = true},
|
|
|
|
|
{from = "/docs/usage/entity-recognition", to = "/usage/linguistic-features#named-entities", force = true},
|
|
|
|
|
{from = "/docs/usage/word-vectors-similarities", to = "/usage/vectors-similarity", force = true},
|
|
|
|
|
{from = "/docs/usage/customizing-tokenizer", to = "/usage/linguistic-features#tokenization", force = true},
|
|
|
|
|
{from = "/docs/usage/language-processing-pipeline", to = "/usage/processing-pipelines", force = true},
|
|
|
|
|
{from = "/docs/usage/customizing-pipeline", to = "/usage/processing-pipelines", force = true},
|
2020-09-03 11:13:03 +00:00
|
|
|
{from = "/docs/usage/training-ner", to = "/usage/training", force = true},
|
2020-04-16 12:45:25 +00:00
|
|
|
{from = "/docs/usage/tutorials", to = "/usage/examples", force = true},
|
|
|
|
|
{from = "/docs/usage/data-model", to = "/api", force = true},
|
|
|
|
|
{from = "/docs/usage/cli", to = "/api/cli", force = true},
|
|
|
|
|
{from = "/docs/usage/lightning-tour", to = "/usage/spacy-101#lightning-tour", force = true},
|
|
|
|
|
{from = "/docs/api/language-models", to = "/usage/models#languages", force = true},
|
|
|
|
|
{from = "/docs/api/spacy", to = "/docs/api/top-level", force = true},
|
|
|
|
|
{from = "/docs/api/displacy", to = "/api/top-level#displacy", force = true},
|
|
|
|
|
{from = "/docs/api/util", to = "/api/top-level#util", force = true},
|
|
|
|
|
{from = "/docs/api/features", to = "/models/#architecture", force = true},
|
|
|
|
|
{from = "/docs/api/philosophy", to = "/usage/spacy-101", force = true},
|
|
|
|
|
{from = "/docs/usage/showcase", to = "/universe", force = true},
|
2020-08-17 22:49:19 +00:00
|
|
|
{from = "/tutorials/load-new-word-vectors", to = "/usage/linguistic-features", force = true},
|
2020-04-16 12:45:25 +00:00
|
|
|
{from = "/tutorials", to = "/usage/examples", force = true},
|
2020-07-01 19:26:39 +00:00
|
|
|
# Old documentation pages (v2.x)
|
|
|
|
|
{from = "/usage/adding-languages", to = "/usage/linguistic-features", force = true},
|
2020-08-17 22:49:19 +00:00
|
|
|
{from = "/usage/vectors-similarity", to = "/usage/linguistic-features#vectors-similarity", force = true},
|
2020-07-05 14:11:16 +00:00
|
|
|
{from = "/api/goldparse", to = "/api/top-level", force = true},
|
|
|
|
|
{from = "/api/goldcorpus", to = "/api/corpus", force = true},
|
|
|
|
|
{from = "/api/annotation", to = "/api/data-formats", force = true},
|
|
|
|
|
{from = "/usage/examples", to = "/usage/projects", force = true},
|
💫 Update website (#3285)
<!--- Provide a general summary of your changes in the title. -->
## Description
The new website is implemented using [Gatsby](https://www.gatsbyjs.org) with [Remark](https://github.com/remarkjs/remark) and [MDX](https://mdxjs.com/). This allows authoring content in **straightforward Markdown** without the usual limitations. Standard elements can be overwritten with powerful [React](http://reactjs.org/) components and wherever Markdown syntax isn't enough, JSX components can be used. Hopefully, this update will also make it much easier to contribute to the docs. Once this PR is merged, I'll implement auto-deployment via [Netlify](https://netlify.com) on a specific branch (to avoid building the website on every PR). There's a bunch of other cool stuff that the new setup will allow us to do – including writing front-end tests, service workers, offline support, implementing a search and so on.
This PR also includes various new docs pages and content.
Resolves #3270. Resolves #3222. Resolves #2947. Resolves #2837.
### Types of change
enhancement
## Checklist
<!--- Before you submit the PR, go over this checklist and make sure you can
tick off all the boxes. [] -> [x] -->
- [x] I have submitted the spaCy Contributor Agreement.
- [x] I ran the tests, and all new and existing tests passed.
- [x] My changes don't require a change to the documentation, or if they do, I've added all required information.
2019-02-17 18:31:19 +00:00
|
|
|
# Rewrite all other docs pages to /
|
|
|
|
|
{from = "/docs/*", to = "/:splat"},
|
|
|
|
|
# Updated documentation pages
|
2020-04-16 12:45:25 +00:00
|
|
|
{from = "/usage/resources", to = "/universe", force = true},
|
|
|
|
|
{from = "/usage/lightning-tour", to = "/usage/spacy-101#lightning-tour", force = true},
|
|
|
|
|
{from = "/usage/linguistic-features#rule-based-matching", to = "/usage/rule-based-matching", force = true},
|
|
|
|
|
{from = "/models/comparison", to = "/models", force = true},
|
2019-03-23 14:45:02 +00:00
|
|
|
{from = "/api/#section-cython", to = "/api/cython", force = true},
|
|
|
|
|
{from = "/api/#cython", to = "/api/cython", force = true},
|
|
|
|
|
{from = "/api/sentencesegmenter", to="/api/sentencizer"},
|
2019-03-19 13:07:00 +00:00
|
|
|
{from = "/universe", to = "/universe/project/:id", query = {id = ":id"}, force = true},
|
|
|
|
|
{from = "/universe", to = "/universe/category/:category", query = {category = ":category"}, force = true},
|
2019-10-08 13:39:38 +00:00
|
|
|
# Renamed universe projects
|
2020-10-16 13:46:34 +00:00
|
|
|
{from = "/universe/project/spacy-pytorch-transformers", to = "/universe/project/spacy-transformers", force = true},
|
|
|
|
|
# Old model pages
|
|
|
|
|
{from = "/models/en-starters", to = "/models/en", force = true},
|
💫 Update website (#3285)
<!--- Provide a general summary of your changes in the title. -->
## Description
The new website is implemented using [Gatsby](https://www.gatsbyjs.org) with [Remark](https://github.com/remarkjs/remark) and [MDX](https://mdxjs.com/). This allows authoring content in **straightforward Markdown** without the usual limitations. Standard elements can be overwritten with powerful [React](http://reactjs.org/) components and wherever Markdown syntax isn't enough, JSX components can be used. Hopefully, this update will also make it much easier to contribute to the docs. Once this PR is merged, I'll implement auto-deployment via [Netlify](https://netlify.com) on a specific branch (to avoid building the website on every PR). There's a bunch of other cool stuff that the new setup will allow us to do – including writing front-end tests, service workers, offline support, implementing a search and so on.
This PR also includes various new docs pages and content.
Resolves #3270. Resolves #3222. Resolves #2947. Resolves #2837.
### Types of change
enhancement
## Checklist
<!--- Before you submit the PR, go over this checklist and make sure you can
tick off all the boxes. [] -> [x] -->
- [x] I have submitted the spaCy Contributor Agreement.
- [x] I ran the tests, and all new and existing tests passed.
- [x] My changes don't require a change to the documentation, or if they do, I've added all required information.
2019-02-17 18:31:19 +00:00
|
|
|
]
|