stackabletech / stackabletech/documentation
Guidance on when to use which products
Nobody has claimed this yet.
- Dominant language
- CSS
- Stars
- 13
- Forks
- 14
- Avg merge
- 4d 8h
- Merged PRs (30d)
- 10
Description
Currently our documentation kind of split between mentalities of "we provide a grab bag of tools that you already know how to use" and "we provide this example to cover this one specific use case" (often trying to show off as much as possible of the platform).
We could do a much better job at helping users guide themselves to the right tools for their given use case. This is especially bad since we have multiple cases where multiple tools we provide have a decently wide overlap (Spark/NiFi/Airflow, Trino/Druid/HBase, HDFS/S3/Minio (which isn't part of our platform per se, but is part of many demos)).
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.
Research direction
No files, tests, or entry points are named; start by reviewing the existing documentation and examples covering Spark/NiFi/Airflow, Trino/Druid/HBase, and HDFS/S3/Minio. Done means users can choose the appropriate tool for a stated use case despite these overlaps.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- spark
- Domain
- data-engineering, documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100