MLSAKIIT / MLSAKIIT/ComposeGenie

Frontend: UI Design Suggestions

Open
#8 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Frontend
Dominant language
TypeScript
Stars
4
Forks
4
PR merge metrics
No merged PRs in 30d

Description

Is your feature request related to a problem? Please describe.
The frontend currently lacks a polished UI design. Users and contributors have no visual guidelines, making it harder to ensure a consistent look and feel across pages.

Describe the solution you'd like
We would like to collect UI design suggestions for the frontend. This could include:

  • Color palettes and themes
  • Layout mockups for Dashboard, Catalog, Composer pages
  • Component styling (buttons, cards, tables)
  • UX improvements and interactive elements

Describe alternatives you've considered

  • Using default component libraries only (but custom designs improve user experience).
  • Copying other UI templates without feedback (less inclusive).

Use Case
This allows designers and contributors to propose visually appealing and user-friendly designs that can later be implemented in React/Tailwind.
It encourages community collaboration and ensures the final frontend is both functional and attractive.

Additional context

  • You can share sketches, Figma links, screenshots, or written descriptions.
  • All suggestions are welcome — creativity is encouraged!
  • If possible, attach references or inspiration links to make the vision clearer.

💡 Note: This issue is a community brainstorming space — feel free to comment with ideas, mockups, or references.

Contributor guide

Open the 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.

Research direction

No files or tests are named. Start by reviewing the frontend's Dashboard, Catalog, and Composer pages, then collect concrete UI proposals such as palettes, layouts, component styling, or UX changes. Done means the community has agreed on usable mockups, references, or written design guidance for later implementation.

Written by the indexing model from the issue text.

Assessment

Tech stack
react, tailwindcss, typescript
Domain
design, frontend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.