Skip to content

Good first issue: improve one workflow or docs path #7

Description

@rpelevin

Frontsmith needs narrow, practical contributions that make the first-run and approval-before-action flow easier to understand.

Good first contribution options:

  • clarify the first-run setup path;
  • improve an operator-facing workflow doc;
  • improve a generated Markdown artifact;
  • make the approval-before-action boundary easier to understand;
  • add focused tests for a workflow command;
  • improve the agency handoff path without adding live integrations by default.

Stay inside the v1.0 boundary: one repo, one local service business, one launchable website, front-office workflows, and explicit approval before live action.

Avoid broad SaaS, auth, billing, CRM, accounting, payment, or live integration work unless a separate issue explicitly scopes it.

Metadata

Metadata

Assignees

No one assigned

    Labels

    activationActivation sprint feedback and adoption workdocumentationImprovements or additions to documentationgood first issueGood for newcomershelp wantedExtra attention is needed

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions