nextlevelbuilder / nextlevelbuilder/ui-ux-pro-max-skill

[Feature Request] πŸ™ Would love to see the demo source code open-sourced for learning!

Open
#163 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

agent:github-maintain decision:backlog enhancement maintain:accepted maintain:triaged
Dominant language
Python
Stars
129k
Forks
13.7k
Avg merge
23h 27m
Merged PRs (30d)
23

Description

Hi there! πŸ‘‹

First of all, huge thanks for building UI UX Pro Max β€” it's an incredibly well-crafted project! The design intelligence database with 57 UI styles, 95 color palettes, 56 font pairings, and all the UX guidelines is truly impressive. 🎨

I recently browsed the demo gallery and was blown away by the 39 website demos showcasing different categories (SaaS, Education, E-commerce, Healthcare, Fintech, and many more). The variety of design styles β€” from Glassmorphism to Claymorphism, light and dark modes β€” really demonstrates the power of this tool.

πŸ’‘ Feature Request

I was wondering if there's any possibility of open-sourcing the source code for these demo websites? Having access to the actual code behind these beautiful demos would be an amazing learning resource for the community. Specifically, it would help developers and designers:

  • Learn by example β€” Understanding how different UI styles (Glassmorphism, Claymorphism, AI-Native UI, etc.) are implemented in real code
  • Study best practices β€” Seeing how color palettes, typography, and responsive layouts are applied in production-quality demos
  • Accelerate their workflow β€” Using the demos as reference or starting points for their own projects
  • Deepen understanding β€” Going beyond the "View Demo" to truly grasp the structure and techniques behind each design

πŸ€” Possible Approaches

Of course, I totally understand if there are reasons this might not be feasible. But here are a few ideas that could work:

  1. Separate repo β€” A dedicated repository with all demo source code
  2. Code snippets in docs β€” Adding key code sections to the documentation
  3. Gradual release β€” Open-sourcing a few demos at a time

πŸ™Œ Why This Would Be Valuable

The demo gallery already serves as great visual inspiration, but having the source code would take it to the next level as a learning platform. It would also likely attract more contributors and users to the project!

Thank you so much for considering this, and again, amazing work on the project! Keep it up! πŸš€

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

Start with the demo gallery linked in the issue and inspect how its 39 demos are organized in the project. Decide whether the source should be released in a separate repository, added to documentation, or published gradually; done means the selected demo source is publicly available with enough context for learners to study it.

Written by the indexing model from the issue text.

Assessment

Domain
documentation
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.