We should use the redirect as described in puppet:/modules/fedora-docs/files/redirects.conf instead of linking to specific doc release.
Example: replace "/en-US/Fedora/16/html/Installation_Guide" occurrences by "/install-guide".
actual redirect are: {{{ RewriteRule /accessibility-guide /en-US/Fedora/16/html/Accessibility_Guide [R=301] RewriteRule /deployment-guide /en-US/Fedora/15/html/Deployment_Guide [R=301] RewriteRule /install-guide /en-US/Fedora/19/html/Installation_Guide [R=301] RewriteRule /installation-quick-start-guide /en-US/Fedora/19/html/Installation_Quick_Start_Guide [R=301] RewriteRule /readme-burning-isos /en-US/Fedora/19/html/Burning_ISO_images_to_disc [R=301] RewriteRule /readme-live-image /en-US/Fedora/15/html/Fedora_Live_Images [R=301] RewriteRule /security-guide /en-US/Fedora/19/html/Security_Guide [R=301] RewriteRule /selinux-faq /en-US/Fedora/13/html/SELinux_FAQ [R=301] RewriteRule /selinux-managing-confined-services-guide /en-US/Fedora/13/html/Managing_Confined_Services [R=301] RewriteRule /selinux-user-guide /en-US/Fedora/13/html/Security-Enhanced_Linux [R=301] RewriteRule /technical-notes /en-US/Fedora/16/html/Technical_Notes [R=301] RewriteRule /user-guide /en-US/Fedora/14/html/User_Guide [R=301] RewriteRule /virtualization-guide /en-US/Fedora/13/html/Virtualization_Guide [R=301] RewriteRule /wireless-guide /en-US/Fedora/13/html/Wireless_Guide [R=301] RewriteRule /release-notes/fc1/x86_64 /en-US/Fedora_Core/1/html/Release_Notes_for_64-bit_x86_Systems [R=301] RewriteRule /release-notes/fc1/x86 /en-US/Fedora_Core/1/html/Release_Notes_for_32-bit_x86_Systems [R=301] RewriteRule /release-notes/fc2/x86_64 /en-US/Fedora_Core/2/html/Release_Notes_for_64-bit_x86_Systems [R=301] RewriteRule /release-notes/fc2/x86 /en-US/Fedora_Core/2/html/Release_Notes_for_32-bit_x86_Systems [R=301] RewriteRule /release-notes/fc3/x86_64 /en-US/Fedora_Core/3/html/Release_Notes_for_64-bit_x86_Systems [R=301] RewriteRule /release-notes/fc3/x86 /en-US/Fedora_Core/3/html/Release_Notes_for_32-bit_x86_Systems [R=301] RewriteRule /release-notes/fc4 /en-US/Fedora_Core/4/html/Release_Notes [R=301] RewriteRule /release-notes/fc5 /en-US/Fedora_Core/5/html/Release_Notes [R=301] RewriteRule /release-notes/fc6 /en-US/Fedora_Core/6/html/Release_Notes [R=301] RewriteRule /release-notes/f7 /en-US/Fedora/7/html/Release_Notes [R=301] RewriteRule /release-notes/f8 /en-US/Fedora/8/html/Release_Notes [R=301] RewriteRule /release-notes/f9 /en-US/Fedora/9/html/Release_Notes [R=301] RewriteRule /release-notes/f10 /en-US/Fedora/10/html/Release_Notes [R=301] RewriteRule /release-notes/f11 /en-US/Fedora/11/html/Release_Notes [R=301] RewriteRule /release-notes/f12 /en-US/Fedora/12/html/Release_Notes [R=301] RewriteRule /release-notes/f13 /en-US/Fedora/13/html/Release_Notes [R=301] RewriteRule /release-notes/f14 /en-US/Fedora/14/html/Release_Notes [R=301] RewriteRule /release-notes/f15 /en-US/Fedora/15/html/Release_Notes [R=301] RewriteRule /release-notes/f16 /en-US/Fedora/16/html/Release_Notes [R=301] RewriteRule /release-notes/f17 /en-US/Fedora/17/html/Release_Notes [R=301] RewriteRule /release-notes/f18 /en-US/Fedora/18/html/Release_Notes [R=301] RewriteRule /release-notes/f19 /en-US/Fedora/19/html/Release_Notes [R=301]
RewriteRule /release-notes/f20 /en-US/Fedora/20/html/Release_Notes [R=301] RewriteRule /release-notes /en-US/Fedora/20/html/Release_Notes [R=301]
}}}
Doing so we will never fix these outdated links, IMHO. We should try to update the links and if not possible to point to the installation guide, without filling up the rewrite rules in puppet.
In addition to this what about creating a docs variable to handle easily the version numbers? Actually the variable is the current_ID, could be docs_ID or something similar. Just to avoid having many dead links because the new docs are not pushed yet.
Replying to [comment:1 robyduck]:
Doing so we will never fix these outdated links, IMHO.
Why? I see it that way: - This redirect list has to be up to date.
Therefor, if we use it, it can't go wrong. And there would be more guys looking to keep that list right. It's easier to update the redirect file than maintain our variable, links...
On a second hand, there could not be a docs_ID variable. But many. As there is release note ID, Install Guide ID... And so on.
Got my mind? Is there something that I don't see?
@shaiton - so is the proposal to use the shorter (redirect) urls on the website instead of the full/actual path?
I'm for it!
Like anything, we just need to maintain those rewrite rules.
The other things, we will probably need to do something for stg too, so that we can (somewhat) validate the urls there.
Sijis
Is this still actual also for the new layout?
Login to comment on this ticket.