Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
G
gitlab-ce
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
0
Merge Requests
0
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
Jérome Perrin
gitlab-ce
Commits
33c49944
Commit
33c49944
authored
Jun 02, 2016
by
Dmitriy Zaporozhets
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Add icons and buttons to UI guide
Signed-off-by:
Dmitriy Zaporozhets
<
dmitriy.zaporozhets@gmail.com
>
parent
30524901
Changes
1
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
21 additions
and
1 deletion
+21
-1
doc/development/ui_guide.md
doc/development/ui_guide.md
+21
-1
No files found.
doc/development/ui_guide.md
View file @
33c49944
...
...
@@ -34,3 +34,23 @@ We want GitLab to work well on small mobile screens as well. Size limitations ma
part of the UI for smaller resolutions in favor of a better user experience.
However core functionality like browsing files, creating issues, writing comments, should
be available on all resolutions.
## Icons
*
`trash`
icon for button or link that does destructive action like removing
information from database or file system
*
`x`
icon for closing/hiding UI element. For example close modal window
*
`pencil`
icon for edit button or link
*
`eye`
icon for subscribe action
*
`rss`
for rss/atom feed
*
`plus`
for link or dropdown that lead to page wher eyou create new object (For example new issue page)
## Buttons
*
Button should contain icon or text. Exceptions should be approved by UX designer.
*
Use gray button on white background or white button on gray background.
*
Use red button for destructive actions (not revertable). For example removing issue.
*
Use green or blue button for primary action. Primary button should be only one.
Do not use both green and blue button in one form.
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment