By adding a
redirect_from list of URLs to your Markdown file's YAML frontmatter, this plugin creates client-side redirects for all of them at build time, with Gatsby's
createRedirect used under the hood.
By combining this plugin with gatsby-plugin-meta-redirect, you get simple server-side redirects from your
redirect_from lists out of the box. You can also combine it with any other plugin picking up Gatsby
createRedirect calls to get proper SEO-friendly server-side redirects for your hosting provider.
Table of Contents
- Gatsby v2
- Markdown files delivered from gatsby-transformer-remark
npm i gatsby-redirect-from gatsby-plugin-meta-redirect
Then load the plugin along with e.g. gatsby-plugin-meta-redirect from your
'gatsby-plugin-meta-redirect' // make sure this is always the last one
In your Markdown file's YAML frontmatter, use the key
redirect_from followed by a list:
title: Aperture File Types
# note: trailing slashes are required
More explanations and options, all about server-side redirects, and additional plugins which can be used in combination with gatsby-redirect-from.
# production build
npm run build
# publishing to npm & GitHub releases
# uses https://github.com/webpro/release-it
npm run release
The MIT License
Copyright (c) 2020 Matthias Kretschmann
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Say thanks with BTC:
Say thanks with ETH: