Category: Usage #15
Labels
No labels
bug
contribution welcome
duplicate
enhancement
good first issue
help wanted
invalid
question
upstream
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
redict/redict-doc#15
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
One thing that always frustrated me about the Redis documentation is that there are some really interesting patterns, but they are pretty hidden. I want us to promote them to a more prominent page in our documentation on redict.io. Let's put a “Usage” category in the navigation next to commands and modules. I would then remove the pattern from the command documentation, and instead link from the command to the pattern.
Patterns that have documentation:
commands/setbit.md)docs/manual/patterns/bulk-loading.md)commands/rpoplpush.md,commands/lmove.md,commands/brpoplpush.md, andcommands/blmove.md)commands/incr.md)docs/manual/patterns/distributed-locks.md)commands/expire.md)commands/incr.md)commands/bitcount.mdandcommands/bitop.md)commands/rpoplpush.md,commands/lmove.md,commands/brpoplpush.md, andcommands/blmove.md)docs/manual/patterns/indexes/index.md)commands/append.md)docs/manual/patterns/twitter-clone.md)commands/zrangebyscore.md)Happy to work on that, if we agree that this is a good idea. It also raises the question if I can just create those files in the redict.io repo, and remove them here.
I was thinking about organizing this content under "Usage", rather than "Patterns". Thoughts?
Good idea! Allows us to put the more tutorial-like things there as well, without needing discuss if they are a "pattern".
Category: Patternto Category: UsageAnother alternative would be "Guides"
Note: I am incorporating scripting API and modules API documentation under their respective sections in the established hierarchy.
@ddevault Do you prefer "Usage" or "Guides"? I'm okay with both, and can start the migration if you give me the thumbs up!
I think Usage is more general here.