docs: rename demos and make them more use case oriented
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- kafka
- Domain
- content, documentation
Research direction
The issue names no files or tests, so first locate the demos and the entry for nifi-kafka-druid-water-level-data. Review the current demo names against the proposed use-case-oriented naming, then rename the relevant demos consistently. Done means the names emphasize the general problem rather than the tools or dataset.
Written by the indexing model from the issue text.
Description
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.
- Dominant language
- Jupyter Notebook
- Stars
- 3
- Forks
- 13
- Avg merge
- 2d 20h
- Merged PRs (30d)
- 2
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from stackabletech/demos
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
stackabletech/demos#402 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
stackabletech/demos#349 ·
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
stackabletech/demos#293 ·
-
release-retro/25.3.0
Difficulty 4/5 3-5 days Newbie friendliness 35/100
stackabletech/demos#208 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
stackabletech/demos#204 ·
All issues in stackabletech/demos
Similar issues
-
community first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs
Difficulty 1/5 Under an hour Newbie friendliness 95/100
-
Ecosystem: ClawMetry — the Qwen Code reader is now free and open source (follow-up to #9294 / #9338) Opencategory/integration priority/P3 scope/documentation status/ready-for-human type/feature-request
Difficulty 1/5 Under an hour Newbie friendliness 84/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
TheOdinProject/curriculum#31408 ·
-
archived coursework help wanted scope: curriculum
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
freeCodeCamp/freeCodeCamp#70260 · 1 comment ·
-
雪鸿集 Open待处理 申请收录
Difficulty 1/5 Under an hour Newbie friendliness 72/100
travellings-link/travellings#4000 · 1 comment ·