info/beautiful-docs
1
0
Fork 0
mirror of https://github.com/PharkMillups/beautiful-docs.git synced 2025-09-01 21:22:44 +02:00
Code Issues Releases Wiki Activity

a few link fixes

Browse Source
This commit is contained in:
Mark Phillips
2012-01-04 14:48:02 -08:00
parent a2d086a7b2
commit 2aad480af3
1 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
README.md
View File

@@ -12,10 +12,10 @@ This should be updated fairly regularly. As usual, **pull requests are encourage
* [Redis Commands](http://redis.io/commands) - Most of the Redis docs are exceptional, but this section really epitomizes the combination of good design and usability. And all the individual command pages give you the ability to test things out without leaving the page. Pretty close to perfect.
* [BrightBox Developer Docs](docs.brightbox.com) - Clean design, easy to navigate, very in-depth.
* [Riaknostic](riaknostic.basho.com) - Made possible by [Bootstrap](https://github.com/twitter/bootstrap), this is a great example of a project homepage that doubles as a documentation teaser.
* [Riaknostic](http://riaknostic.basho.com) - Made possible by [Bootstrap](https://github.com/twitter/bootstrap), this is a great example of a project homepage that doubles as a documentation teaser.
* [GitHub Developer Docs](http://developer.github.com/v3/) - I don't always get excited about accordion-based navigation, but when I do...
* [Dropwizard](http://dropwizard.codahale.com/) - Beautiful and concise; another Bootstrap joint.
* [Riak Pipe README](github.com/basho/riak_pipe) - The simplicity of READMEs means that you can't obscure shitty content with flashy design. This one is written by my Basho colleague [Bryan Fink](https://twitter.com/#!/hobbyist) and should be committed to memory as an excellent example of how to write READMEs.
* [Riak Pipe README](https://github.com/basho/riak_pipe) - The simplicity of READMEs means that you can't obscure shitty content with flashy design. This one is written by my Basho colleague [Bryan Fink](https://twitter.com/#!/hobbyist) and should be committed to memory as an excellent example of how to write READMEs.
* [Learn You Some Erlang](http://learnyousomeerlang.com/) (via [@lenary](https://twitter.com/lenary))
* [Django Documentation](https://docs.djangoproject.com/en/1.3/) (via [@bretthoerner](https://twitter.com/bretthoerner))
* [Erldocs.com](http://erldocs.com/) (via [@bradfordw](https://twitter.com/#!/bradfordw))