docs: add design guidelines and UI theme requirements#2
Open
AbuJulaybeeb wants to merge 1 commit into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What was done:
Created DESIGN_GUIDELINES.md outlining the project's official color palette, typography preferences, and preferred UI aesthetics (glassmorphism, subtle gradients, etc.).
Outlined contribution rules for modular UI components and Tailwind utilization.
Added a highly visible link to the new guidelines inside the README.md under the Contribution section.
Why it was done:
To officially answer community requests regarding existing theme requirements and preferred UI direction for the landing page.
Establishes a concrete stylistic foundation so that contributors can safely open UI PRs without breaking the premium, space-themed visual experience.
How it was verified:
Verified markdown formatting and ensured all color hexes/Tailwind tokens align perfectly with the current tailwind.config.js.
closes #1