Doc change: What does DCli do different than just creating a Dart CLI project?
Nobody has claimed this yet.
- Dominant language
- Dart
- Stars
- 265
- Forks
- 30
- PR merge metrics
- No merged PRs in 30d
Description
You explain why DCli is different from other CLIs by pointing to the fact it is based on Dart. However, what you don't do a good job of explaining why people should use it instead of just creating a new Dart CLI project. You might want to include a section in the readme that explains that. Especially since it's on pub.dev ... where everyone is already using Flutter and Dart.
Contributor guide
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
Start in the repository README by reviewing the existing explanation of how DCli differs from other CLI options. Add a focused section explaining why Dart and Flutter users should choose DCli instead of creating a new Dart CLI project, with wording suitable for the pub.dev audience. Done means the comparison and motivation are clear in the README.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- dart
- Domain
- cli, documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100