Why?
Because, people with no knowledge about GitHub and Markdown files can land directly to repository's home from some source and might not know where the content is. Also, it might look better this way.

And, you can link the contribution.md and authors.md, containing the corresponding information, to the README.md.

"Python API for various web services" in API and Web Services is redirecting to inappropriate content.

For topic: https://github.com/kirang89/pycrumbs#mobile-development

http://archlinux.me/dusty/2013/06/13/creating-an-application-in-kivy-part-1/ no longer works. With a bit of search, I found http://buchuki.com/index.php/2013/06/13/creating-an-application-in-kivy-part-1/ which I think is the same

I´ve seen that at many other projects. It helps at points like search-ability. What do you think?

Or at least include a warning. Why? I'm one of the people cleaning up the mess it causes and I'm also one of the maintainers. See the warning: http://www.djangobook.com/en/2.0/index.html

A warning about this edition
The community edition of The Django Book is in transition. While the book mentions Django version 1.4 in places, the vast majority of the book is for Django version 1.0, which was released over four years ago. Therefore this resource is extremely out of date and, until the book is finished being updated, we ask that, at this time, djangobook.com not be used for educational purposes.

This book was originally published by Apress in 2009 and covered Django version 1.0. Since then it has languished and, in places, is extremely out of date. We are working on getting the book updated to cover Django versions 1.4, 1.5, and beyond. But we need your help, we’re making this book — warts and all — open source in the hopes that it will find love as a community project.

Link -
https://www.khanacademy.org/science/computer-science

Type -
Beginner's level tutorial

Format -
Video (YouTube)

The list is huge but couldn't find any reference to Khan Academy. Hence, the above link would be a nice addition.

Sorry, didn't have time to submit a PR, hence created a new issue!