docs: rename demos and make them more use case oriented

未关闭
#16 1 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
3/5
预计耗时
1-2 天
新手友好度
35/100
Issue 类型
文档
描述清晰度
基本清楚
活跃度
停滞
技术栈
kafka
领域
content, documentation

调研方向

该 issue 没有列出任何文件或测试，因此首先找到各个 demo 以及 nifi-kafka-druid-water-level-data 的条目。根据提议的面向用例的命名方式检查当前的 demo 名称，然后统一重命名相关的 demo。完成的标准是名称强调一般性问题，而不是工具或数据集。

由索引模型根据 Issue 内容生成。

描述

Currently the demos are named based on the tech that is used in them. This is good if you're a potential user that already has a Stack of tools that you want to migrate, or if you already have a deeper technical understanding of the tools you might need.

I would propose that we instead rename i.e. nifi-kafka-druid-water-level-data to "Real time stream data analysis and visualization" or something like that. Less focus on the tools and this particular dataset (water levels) and more on the general problem it solves. This way it is more interesting to people that might not know this specific stack, but also to people that might have an existing pipeline that does just this, but maybe with different tools. They might still be interested in using stackable and also swapping out some of their tools in their pipeline while they are at it.

主要语言
Jupyter Notebook
星标
3
派生
13
平均合并
2 天 20 小时
30 天内合并 PR
2

贡献指南

这个仓库没有索引到贡献指南

从这里开始

  1. 先读完整个 Issue，再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库，在一个分支上完成修改。
  4. 提交 Pull Request，并在描述里引用这个 Issue 编号。

stackabletech/demos 的其他 Issue

查看 stackabletech/demos 的全部 Issue

相似的 Issue

更多 Content Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。