Issue #1470
closed
Users are finding our v1 wiki again, due to it not being excluded by robots.txt
Description
We have twice gotten Pulp's v1 wiki to be excluded from search engines via robots.txt, and it has now been removed twice:
https://fedorahosted.org/robots.txt
We could pursue asking fedorahosted.org to add us back to the exclusions, but I am concerned that it might be reverted again. We need to do something more drastic with our v1 wiki to prevent users from finding it when searching for Pulp questions. There are many possible solutions, including removing the wiki entirely, or archiving it within our new docs somehow. Another possible solution is to invest more effort in making those docs very clearly for an unsupported release, perhaps with a giant watermark. It is believed that there are still some Pulp v1 users out there, so we probably should make it possible to access the v1 docs.
Related issues
Updated by rbarlow over 8 years ago
- Related to Issue #651: The website links to the wiki, which has outdated information added
Updated by bmbouter over 8 years ago
+1 to not doing the robots.txt again.
I think the wiki can be put into read-only mode. If that is the case, we should consider making an index/archive of the site and taking it down from being a site that is served page by page. This will resolve the root problem which is that search engines are directing users into these docs, while still allowing them to be available. We could then distribute this asset from a page in our current docs called, "legacy docs" or similar. We've had so many different docs sites we're going to need a page like this anyway.
Updated by mhrivnak over 8 years ago
- Triaged changed from No to Yes
- Tags Documentation added
Updated by bmbouter about 5 years ago
- Status changed from NEW to CLOSED - WONTFIX
Updated by bmbouter about 5 years ago
Pulp 2 is approaching maintenance mode, and this Pulp 2 ticket is not being actively worked on. As such, it is being closed as WONTFIX. Pulp 2 is still accepting contributions though, so if you want to contribute a fix for this ticket, please reopen or comment on it. If you don't have permissions to reopen this ticket, or you want to discuss an issue, please reach out via the developer mailing list.
.