1
0
mirror of https://github.com/PharkMillups/beautiful-docs.git synced 2025-08-24 22:25:59 +02:00

Use https in Redis Commands link

This commit is contained in:
Matheus Felipe
2022-04-13 14:13:50 -03:00
committed by GitHub
parent 690e78deb8
commit b5ddb240f9

View File

@@ -12,7 +12,7 @@ This should be updated fairly regularly. As usual, **pull requests are encourage
### And Now For The Docs ### And Now For The Docs
* [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. * [Redis Commands](https://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.
* [GitHub Developer Docs](http://developer.github.com/v3/) - I don't always get excited about accordion-based navigation, but when I do... * [GitHub Developer Docs](http://developer.github.com/v3/) - I don't always get excited about accordion-based navigation, but when I do...
* [Dropwizard](http://www.dropwizard.io/) - Beautiful and concise; another Bootstrap joint. (contributed by [mrtazz](https://twitter.com/#!/mrtazz)).) * [Dropwizard](http://www.dropwizard.io/) - Beautiful and concise; another Bootstrap joint. (contributed by [mrtazz](https://twitter.com/#!/mrtazz)).)
* [Riak Pipe README](https://github.com/basho/riak_pipe/blob/develop/README.org) - 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/blob/develop/README.org) - 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.