Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Outdated documentation should be invisible to Google #3559

Closed
agrimm opened this issue Nov 8, 2011 · 9 comments
Closed

Outdated documentation should be invisible to Google #3559

agrimm opened this issue Nov 8, 2011 · 9 comments
Assignees
Labels

Comments

@agrimm
Copy link
Contributor

agrimm commented Nov 8, 2011

When you search for 'ruby starts_with' (sans quotes) with Google, http://as.rubyonrails.org/classes/ActiveSupport/CoreExtensions/String/StartsEndsWith.html comes up as the tenth hit, and is the first hit providing documentation. The documentation in as.rubyonrails.org is horribly out of date - it was last updated in 2008.

as.rubyonrails.org should ideally be deleted with users encouraged to use api.rubyonrails.org , but failing that, the domain should be made invisible to Google, possibly via robots.txt, so that Rails newbies don't end up using outdated documentation.

@sarahhodne
Copy link
Contributor

I only learned a few weeks ago that as, ar, etc. were out of date, so it should at least have some banner on top saying "this documentation is out of date, please use api.rubyonrails.org instead".

@carlosantoniodasilva
Copy link
Member

I think these "out of date" docs should redirect to api.rubyonrails.org for now, so we would keep all links over the internet working, pointing to some real docs, and we could get rid of the "out of date" ones.

@fxn @vijaydev thoughts on that?

@fxn
Copy link
Member

fxn commented Apr 2, 2012

I don't mind about returning 404 for these documents... @vijaydev what do you think about not generating guides unless they are published?

@vijaydev
Copy link
Member

vijaydev commented Apr 2, 2012

@fxn not published meaning all WIP and stale guides? Sounds good not to generate the stale guides (though we don't have a way to segregate them currently), but I think WIP guides are useful if available.

@isaacsanders
Copy link
Contributor

+1

1 similar comment
@jeroeningen
Copy link

👍

@joanwolk
Copy link

WIP guides can be really helpful, even if they're not finished. I got a lot of help from one about mailers a while ago. I'd be in favor of giving them proper links, noting they're still in progress but allowing them some recognized status on the site.

@fxn
Copy link
Member

fxn commented Dec 8, 2012

This is in my TODO list, I'll modify the scripts in the docs sever not to generate WIP guides. WIP guides are in the repo only for the convenience of authors, their content cannot leak, and time has proven they do in web searches even if not linked in the table of contents.

@ghost ghost assigned fxn Dec 8, 2012
@fxn
Copy link
Member

fxn commented Apr 17, 2013

I am closing this one since the old subdomains are down.

@fxn fxn closed this as completed Apr 17, 2013
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

8 participants