WIP: About Page #2

moonglum commented 2024年03月22日 22:54:05 +01:00

One of the difficulties of understanding a system like Redict is to show the simplicity and elegance of the system, while showing the power and versatility that comes from it. My approach here would be to go through the data types, show 1–3 commands for each of them, and give examples for usage. One thing I noticed in the past when working with clients using Redis was that they had no idea how broad the use cases of the system are.

Starting the explanation by going through the data types makes sense to me. Understanding that the key is always a string, but the value can be one of many types, which influences which commands you can use. This approach worked well for me in the past when I presented Redis to colleagues and clients in the past.

Please tell me if this goes into the right direction. If so, I will continue working on this page.

One of the difficulties of understanding a system like Redict is to show the simplicity and elegance of the system, while showing the power and versatility that comes from it. My approach here would be to go through the data types, show 1–3 commands for each of them, and give examples for usage. One thing I noticed in the past when working with clients using Redis was that they had no idea how broad the use cases of the system are. Starting the explanation by going through the data types makes sense to me. Understanding that the key is always a string, but the value can be one of many types, which influences which commands you can use. This approach worked well for me in the past when I presented Redis to colleagues and clients in the past. Please tell me if this goes into the right direction. If so, I will continue working on this page.

ddevault commented 2024年03月23日 11:20:34 +01:00

Hm, I'm not sure about this. I have a different approach in mind for the "pitch", or "getting started" kinds of content. For now can we focus on the practical?

Let me write up an issue in more detail which explains what I think we should add, and see what you think of the plan.

Hm, I'm not sure about this. I have a different approach in mind for the "pitch", or "getting started" kinds of content. For now can we focus on the practical? Let me write up an issue in more detail which explains what I think we should add, and see what you think of the plan.

moonglum commented 2024年03月24日 22:40:12 +01:00

Works for me! 👍

Works for me! 👍

ddevault commented 2024年03月24日 22:52:36 +01:00

I think what would be good now is organizing the contents of redict-doc and getting it onto redict.io. There are a bunch of issues on the redict-doc repo to look at :)

I think what would be good now is organizing the contents of [redict-doc](https://codeberg.org/redict/redict-doc) and getting it onto redict.io. There are a bunch of issues on the redict-doc repo to look at :)

moonglum commented 2024年03月25日 22:06:33 +01:00

@ddevault Can you briefly explain the difference between or roles of redict-doc vs. redict.io? 🤔

@ddevault Can you briefly explain the difference between or roles of redict-doc vs. redict.io? 🤔

ddevault commented 2024年03月26日 10:03:56 +01:00

@moonglum talked about that here:

redict/redict-doc#9 (comment)

@moonglum talked about that here: https://codeberg.org/redict/redict-doc/issues/9#issuecomment-1712863

moonglum commented 2024年04月01日 13:32:56 +02:00

Closed in favor of our Usage section.

Closed in favor of our Usage section.