Skip to content

[v1.0] Clarify base-cli positioning, onboarding, and PyPI discoverability #188

Description

@codeforester

Goal

Make a first-time adopter understand what base-cli is, when to choose it, and how to run a useful CLI in under five minutes.

Background

The framework has a strong lifecycle model, but its current public presentation does not yet make the differentiation, supported consumer patterns, or first successful run obvious. This directly limits discovery and adoption.

Scope

Rewrite the README and PyPI-facing metadata around a concise positioning statement; add a five-minute Click/Typer quickstart; add a decision/comparison matrix against adjacent Python CLI frameworks; document the architecture and extension points at the right level; add accurate PyPI keywords and links to a maintained starter/template path.

Acceptance Criteria

  • A one-sentence positioning statement is visible above the fold.
  • A clean-install quickstart reaches a working command.
  • The comparison matrix names criteria and avoids unsupported claims.
  • Package metadata contains relevant search terms.
  • Links and examples are validated in CI.
  • No runtime API behavior changes are introduced.

Validation

Run the documentation validator/build in strict mode; build the package and inspect rendered metadata; execute the quickstart in a clean virtual environment.

Non-Goals

Do not replace Click/Typer, promise unsupported features, or make unverified adoption/customer claims.

Project Fields

  • Status: Backlog
  • Priority: P1
  • Area: Product
  • Initiative: v1.0 Readiness
  • Size: M

Ownership

Metadata

Metadata

Assignees

Labels

enhancementNew feature or product improvement

Type

No type

Projects

Status
Done

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions