Please check the status of this specification in Launchpad before editing it. If it is Approved, contact the Assignee or another knowledgeable person before making changes.
Launchpad Entry: external-links-redirects
Packages affected: ubuntu-docs
The report of bug 118741 turned into this spec: Links in documentation to external webpages should go through a redirect-page powered by Ubuntu in order to prevent link breakages.
All external links will now be handled through Ubuntu-controlled redirect pages, which should mean a large decrease in the number of dead links in the official Ubuntu Documentation.
Routing all external links through Ubuntu-controlled redirect-pages would make it easier for the Documentation Team to change the links in case the external URL changes.
- Phillipe included a link to a project's website in some documentation he wrote. However, the project rebranded after the docs were released, and changed their domain name in doing so. Unfortunately, the redirect they set up was broken; users got '404' messages when they clicked the link in the docs, couldn't get to the extra information and so reported a load of bugs. If the link had been sent through a redirecting service, Phillipe would have been able to edit the URL and fix the issue immediately.
Marvin linked to a useful howto guide in a document he wrote for Edubuntu. The domain which the document was hosted on was later bought by another company, and the document was replaced. Now, instead of getting a useful howto guide, the kids using Edubuntu get a load of pictures of ladies doing unspeakable things. Some go blind (we're talking really unspeakable things here). If the link had been sent through a redirecting service, Marvin could have simply removed the link and displayed an error message instead, which is less likely to scar the children for life.
- Users will not take exception to being redirected through the ubuntu.com domain
- A small script will be permitted to be added to an Ubuntu webserver by the admins
A small web application should be created to handle the following tasks:
- Redirecting to another URL
- Adding a new URL which can be redirected to
- Editing an existing URL
- Displaying an error message when a redirected-to page is found to no-longer be available (can be flagged manually)
Benefits of the alternate suggestion:
- automatically provides updatability to external links using the current software
- feeds back directly to the online documentation's accuracy and currentness
- helps keep all links in sync by reducing duplicates
- still possible to add tools to report and check for links to the online help, benefiting both
- for example one tool could show all pages that use a given address to check for other places to fix
This section should describe a plan of action (the "how") to implement the changes discussed. Could include subsections like:
No user interface is required on the user-side. The user should be transparently redirected through the ubuntu.com domain to the relevant website. An exception is when an URL is no longer available - a standard error message should be shown instead.
A small set of PHP scripts should be sufficient to implement this feature. The scripts will need access to a database table to store the URLs in.
Users should be unable to change URLs themselves, although it may be useful to allow them to mark links as being dead. Only specific, trusted people should be allowed to add or make changes to URLs in the database, to prevent misuse. The table should be backed-up regularly in case it is compromised at a later date.
- Previous Ubuntu releases can't really be changed, so should just be left with non-redirected links in the documentation
- All URLs in the current ubuntu-docs SVN trunk should be added to the redirecting service, and the URLs in the documentation should be changed to corresponding redirected URLs.
It's important that we are able to test new features, and demonstrate them to users. Use this section to describe a short plan that anybody can follow that demonstrates the feature is working. This can then be used during CD testing, and to show off after release.
This need not be added or completed until the specification is nearing beta.
This should highlight any issues that should be addressed in further specifications, and not problems with the specification itself; since any specification with problems cannot be approved.
- No outstanding issues at the moment
BoF agenda and discussion
Use this section to take notes during the BoF; if you keep it in the approved spec, use it for summarising what was discussed and note any options that were rejected.
- No BoF notes at the moment