Improve UI/UX: Improve landing page usability and onboarding clarity

Open
  • Is something wrong?
#17 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
python
Domain
design, frontend, web-dev

Research direction

Start by inspecting the landing page, especially the GitHub sign-in action and repository list. Define a focused first iteration from the proposed onboarding, workflow explanation, layout, or repository-list improvements, and consider the work done when first-time visitors can understand the CLA workflow and available actions.

Written by the indexing model from the issue text.

Description

Hi maintainers,
I recently came across this project while exploring areas where I could contribute, and I wanted to suggest a small UX improvement regarding the landing page.

Currently, the landing page presents only a single primary action : Sign in with GitHub, along with a list of repositories. As a first-time visitor, I found it slightly difficult to understand the overall workflow and what actions would become available after signing in.

Observations
  • The page does not clearly explain:
    • What a CLA is in the context of this system.
    • What users can do after authentication.
    • Whether signing in is required for all use cases.
  • The long repository list appears without any interaction or context, which makes it harder to understand its relevance.
  • There is no visible onboarding or “How it works” section for new users.
Why this matters

For contributors who are evaluating the project or only intend to work on UI or documentation, the lack of onboarding context can make the application feel more complex than it actually is.

Suggested improvements
  • Add a short “How it works” section on the landing page explaining the CLA workflow.
  • Provide minimal onboarding context before requiring GitHub authentication.
  • Introduce basic layout structure (e.g., a small hero section, feature highlights, or a short explanation of the signing process).
  • Optionally replace the raw repository list with a searchable or collapsible layout.

If this sounds reasonable, I would be happy to work on a first iteration of this improvement!

Thanks for the great project and for your time!

Dominant language
Python
Stars
8
Forks
15
Avg merge
7m
Merged PRs (30d)
1

Getting set up

  • Ships a Dockerfile or Docker Compose file
  • No pull request template
  • No contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from psf/clabot

All issues in psf/clabot

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.