max/nix-super
1
0
Fork 0
mirror of https://github.com/privatevoid-net/nix-super.git synced 2024-11-10 00:08:07 +02:00
Code Issues Projects Releases Packages Wiki Activity Actions
nix-super/doc/manual/_redirects

41 lines
1.6 KiB
Text
Raw Normal View History

add path based redirects up to now, those were managed outside of this repo, which as unsurprisingly a real hassle to deal with if one wanted to prevent URLs from breaking when moving pages around. this change removes a large part of the friction involved in moving content in the Nix manual. possible next steps for further automation: - check for content that moved and warn if it's not reachable from links that were valid prior to a change - create redirect rules automatically based on this information
2023-11-27 09:33:03 +02:00
# redirect rules for paths (server-side) to prevent link rot.
# see ./redirects.js for redirects based on URL fragments (client-side)
#
# concrete user story this supports:
# - user finds URL to the manual for Nix x.y
# - Nix x.z (z > y) is the most recent release
# - updating the version in the URL will show the right thing
#
# format documentation:
# - https://docs.netlify.com/routing/redirects/#syntax-for-the-redirects-file
# - https://docs.netlify.com/routing/redirects/redirect-options/
#
# conventions:
# - always force (<CODE>!) since this allows re-using file names
# - group related paths to ease readability
Avoid `<name>/<name>` in documentation URLs They are redundant and look weird.
2023-11-27 15:48:11 +02:00
# - keep in alphabetical/wildcards-last order, which will reduce version control conflicts
add path based redirects up to now, those were managed outside of this repo, which as unsurprisingly a real hassle to deal with if one wanted to prevent URLs from breaking when moving pages around. this change removes a large part of the friction involved in moving content in the Nix manual. possible next steps for further automation: - check for content that moved and warn if it's not reachable from links that were valid prior to a change - create redirect rules automatically based on this information
2023-11-27 09:33:03 +02:00
# - redirects that should have been there but are missing can be inserted where they belong
Avoid `<name>/<name>` in documentation URLs They are redundant and look weird.
2023-11-27 15:48:11 +02:00
/advanced-topics/advanced-topics /advanced-topics 301!
/command-ref/command-ref /command-ref 301!
/contributing/contributing /contributing 301!
add path based redirects up to now, those were managed outside of this repo, which as unsurprisingly a real hassle to deal with if one wanted to prevent URLs from breaking when moving pages around. this change removes a large part of the friction involved in moving content in the Nix manual. possible next steps for further automation: - check for content that moved and warn if it's not reachable from links that were valid prior to a change - create redirect rules automatically based on this information
2023-11-27 09:33:03 +02:00
/expressions/expression-language /language/ 301!
/expressions/language-constructs /language/constructs 301!
/expressions/language-operators /language/operators 301!
Avoid `<name>/<name>` in documentation URLs They are redundant and look weird.
2023-11-27 15:48:11 +02:00
/expressions/language-values /language/values 301!
add path based redirects up to now, those were managed outside of this repo, which as unsurprisingly a real hassle to deal with if one wanted to prevent URLs from breaking when moving pages around. this change removes a large part of the friction involved in moving content in the Nix manual. possible next steps for further automation: - check for content that moved and warn if it's not reachable from links that were valid prior to a change - create redirect rules automatically based on this information
2023-11-27 09:33:03 +02:00
/expressions/* /language/:splat 301!
Avoid `<name>/<name>` in documentation URLs They are redundant and look weird.
2023-11-27 15:48:11 +02:00
/installation/installation /installation 301!
add path based redirects up to now, those were managed outside of this repo, which as unsurprisingly a real hassle to deal with if one wanted to prevent URLs from breaking when moving pages around. this change removes a large part of the friction involved in moving content in the Nix manual. possible next steps for further automation: - check for content that moved and warn if it's not reachable from links that were valid prior to a change - create redirect rules automatically based on this information
2023-11-27 09:33:03 +02:00
Avoid `<name>/<name>` in documentation URLs They are redundant and look weird.
2023-11-27 15:48:11 +02:00
/package-management/basic-package-mgmt /command-ref/nix-env 301!
add redirect to new store page
2023-12-01 02:54:48 +02:00
/package-management/channels /command-ref/nix-channel 301!
Avoid `<name>/<name>` in documentation URLs They are redundant and look weird.
2023-11-27 15:48:11 +02:00
/package-management/package-management /package-management 301!
add redirect to new store page
2023-12-01 02:54:48 +02:00
/package-management/s3-substituter /store/types/s3-binary-cache-store 301!
add path based redirects up to now, those were managed outside of this repo, which as unsurprisingly a real hassle to deal with if one wanted to prevent URLs from breaking when moving pages around. this change removes a large part of the friction involved in moving content in the Nix manual. possible next steps for further automation: - check for content that moved and warn if it's not reachable from links that were valid prior to a change - create redirect rules automatically based on this information
2023-11-27 09:33:03 +02:00
Avoid `<name>/<name>` in documentation URLs They are redundant and look weird.
2023-11-27 15:48:11 +02:00
/protocols/protocols /protocols 301!
/release-notes/release-notes /release-notes 301!
Reference in a new issue Copy permalink