Skip to content

[task] Review first-run copy for local GitHub workflow client #15

Closed as not planned
Closed as not planned
[task] Review first-run copy for local GitHub workflow client#15
Labels
area: designUX, visual design, copy, screenshots, and design contribution workflow.good first design issueA scoped design, UX, copy, or documentation task suitable for a first contribution.good first issueA scoped task that is suitable for a first contribution.good for beginnerA student-friendly starter task with clear scope, success criteria, and verification steps.kind: docsDocumentation-only changes or issues.needs: designNeeds UX, visual design, copy, or accessibility input before implementation.status: staleAutomatically marked stale due to inactivity.
Milestone
v0.3.0 - Desktop Workflow Dashboard

Description

@phongndo
phongndo
opened on Apr 28, 2026

Goal

Review and improve first-run copy so the desktop app clearly presents Nexgit as a local GitHub workflow client.

Why this matters

The first screen should not imply Nexgit is a stacked-diff clone, a generic Git GUI, or a finished product. It should honestly explain the pre-alpha GitHub workflow dashboard direction.

Command/API target

Design/comment-only issue. A code PR is optional.

Depends on

Out of scope

  • Do not redesign the whole desktop app.
  • Do not implement app-server GitHub methods.
  • Do not add stacked PR messaging.

Definition of done

  • The contribution includes UX notes, proposed copy, screenshots, or a small copy/doc update.
  • The proposal explains what a first-time user should understand after opening the app.
  • The copy references GitHub workflow state: issues, PRs, checks, reviews, or maintainer queue.

Verification

  • Attach screenshots, a Figma link, or written UX notes.
  • If changing docs or copy in the repo, run pnpm format:prettier:check.

Contributor notes

This is a good first design issue. A useful contribution can be only a comment with screenshots and proposed copy.

Activity

  1. phongndo
    added this to the v0.1.0 - Contributor MVP milestone on Apr 28, 2026
  2. phongndo
    added
    area: designUX, visual design, copy, screenshots, and design contribution workflow.
    kind: docsDocumentation-only changes or issues.
    needs: designNeeds UX, visual design, copy, or accessibility input before implementation.
    good for beginnerA student-friendly starter task with clear scope, success criteria, and verification steps.
    good first design issueA scoped design, UX, copy, or documentation task suitable for a first contribution.
    on Apr 28, 2026
  3. phongndo
    modified the milestones: v0.1.0 - GitHub App-Server Data, v0.3.0 - Desktop Workflow Dashboard on Apr 29, 2026
  4. phongndo
    changed the title [-][task] Review first-run desktop empty state copy[/-] [+][task] Review first-run copy for local GitHub workflow client[/+] on Apr 29, 2026
  5. phongndo
    added
    __placeholder__
    and removed
    area: designUX, visual design, copy, screenshots, and design contribution workflow.
    kind: docsDocumentation-only changes or issues.
    needs: designNeeds UX, visual design, copy, or accessibility input before implementation.
    good for beginnerA student-friendly starter task with clear scope, success criteria, and verification steps.
    good first design issueA scoped design, UX, copy, or documentation task suitable for a first contribution.
    on Apr 29, 2026

  6. 1 remaining item

  7. phongndo
    added
    kind: docsDocumentation-only changes or issues.
    needs: designNeeds UX, visual design, copy, or accessibility input before implementation.
    good for beginnerA student-friendly starter task with clear scope, success criteria, and verification steps.
    good first design issueA scoped design, UX, copy, or documentation task suitable for a first contribution.
    and removed
    __placeholder__
    on Apr 29, 2026

  8. github-actions commented on Apr 29, 2026

    @github-actions
    github-actionsBot
    on Apr 29, 2026 – with GitHub Actions

    This issue needs a small update before triage:

    • Area must be one of Automation, CLI, Core, Desktop, Design, Docs, Protocol, Tests, or TUI so triage automation can route the issue.

    Please edit the issue instead of opening a new one.

  9. github-actions
    added
    needs: complianceThe author or reporter needs to fix template or policy gaps.
    and removed
    area: designUX, visual design, copy, screenshots, and design contribution workflow.
    on Apr 29, 2026
  10. phongndo
    added
    area: designUX, visual design, copy, screenshots, and design contribution workflow.
    good first issueA scoped task that is suitable for a first contribution.
    and removed
    needs: complianceThe author or reporter needs to fix template or policy gaps.
    on Apr 29, 2026

  11. github-actions commented on Jun 1, 2026

    @github-actions
    github-actionsBot
    on Jun 1, 2026 – with GitHub Actions

    This issue has been quiet for a while. If it is still relevant, add context and it will stay open.

  12. github-actions
    added
    status: staleAutomatically marked stale due to inactivity.
    on Jun 1, 2026

  13. github-actions commented on Jun 15, 2026

    @github-actions
    github-actionsBot
    on Jun 15, 2026 – with GitHub Actions

    Closing due to prolonged inactivity. It can be reopened with fresh context.

  14. github-actions
    closed this as not plannedon Jun 15, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    area: designUX, visual design, copy, screenshots, and design contribution workflow.good first design issueA scoped design, UX, copy, or documentation task suitable for a first contribution.good first issueA scoped task that is suitable for a first contribution.good for beginnerA student-friendly starter task with clear scope, success criteria, and verification steps.kind: docsDocumentation-only changes or issues.needs: designNeeds UX, visual design, copy, or accessibility input before implementation.status: staleAutomatically marked stale due to inactivity.

    Type

    No type

    Projects

    No projects

      Milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions