GitHub - IAMME543/Open-But-Polished · GitHub
/" data-turbo-transient="true" />
Skip to content
Search or jump to...
Search code, repositories, users, issues, pull requests...
-->
Search
Clear
Search syntax tips
Provide feedback
--><br>We read every piece of feedback, and take your input very seriously.
Include my email address so I can be contacted
Cancel
Submit feedback
Saved searches
Use saved searches to filter your results more quickly
-->
Name
Query
To see all available qualifiers, see our documentation.
Cancel
Create saved search
Sign in
/;ref_cta:Sign up;ref_loc:header logged out"}"<br>Sign up
Appearance settings
Resetting focus
You signed in with another tab or window. Reload to refresh your session.<br>You signed out in another tab or window. Reload to refresh your session.<br>You switched accounts on another tab or window. Reload to refresh your session.
Dismiss alert
{{ message }}
IAMME543
Open-But-Polished
Public
Notifications<br>You must be signed in to change notification settings
Fork
Star
main
BranchesTags
Go to file
CodeOpen more actions menu
Folders and files<br>NameNameLast commit message<br>Last commit date<br>Latest commit
History<br>14 Commits<br>14 Commits
How To Make It?
How To Make It?
.gitmodules
.gitmodules
Design Principals.md
Design Principals.md
LICENSE
LICENSE
README.md
README.md
Software To Make.md
Software To Make.md
View all files
Repository files navigation
This work is licensed under CC-BY
Open But Polished
Why must an open ecosystem of software have such inconsistency in user-experience, and design language? There should be no reason open software cannot be as polished or as cohesive as proprietary alternatives. Therefore, lets make it polished.
The problem I find with existing solutions such as gnome, is that common tools still aren't first class citizens. Libreoffice doesn't exactly fit in to the design language does it?
This project has an end goal of a cohesively designed linux distribution. But currently that is a yacht problem. The aim currently is to build a suite of apps with a consistent design philosophy(see below).
UX Design Guidelines
Principals (Why)
The guidelines for making guidelines, or as I like to call them are the outlining principals for design implementations and standards.
Standards (What)
Standards are a constrain set for implementations. They determine what is adequate rather than how to implement the standards in a design.
TBD
Implementations (How)
Implementations are the method of achieving a standard given a specific context and tradeoffs, additionally they may evolve over time. Implementations are a reference point to applying standards to a design.
TBD
Existing Apps
Set Things (settings)
About
No description, website, or topics provided.
Resources
Readme
License
CC-BY-4.0 license
Uh oh!
There was an error while loading. Please reload this page.
Activity
Stars
star
Watchers
watching
Forks
forks
Report repository
Releases
No releases published
Packages
Uh oh!
There was an error while loading. Please reload this page.
Contributors
Uh oh!
There was an error while loading. Please reload this page.
You can’t perform that action at this time.