-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Make UI more like other admin apps, prevent accidental publishing #466
Merged
Conversation
This file contains 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
Match the behaviour of other admin apps and use styles provided by the admin gem.
* Remove “hover” style, items aren’t clickable, use striped instead * Add a missing table row element * Add table-header class to highlight headings
Prevent checkboxes from appearing too far left of content. This matches the recommended Bootstrap 3 pattern: http://getbootstrap.com/css/#forms
A row with col-md-12 in this case is the same as no row and no cell.
* Make it harder to accidentally click the wrong one. * Put the more commonly used edit button first. * Hide the publish button altogether when you can’t publish, disabled buttons have proved to be confusing in the past and users continue to try and interact with them
Use a lighter colour to indicate when an item was updated, to make the list of sections or manuals easier to scan.
* Correctly space sections with a consistent vertical rhythm * Use `lead` styles to make summary more readable * Remove collapsible body function, instead restrict height, and don’t show at all unless there is a body * Remove dependencies on govuk_frontend_toolkit – currently the admin template and the toolkit don’t play well together
A date is usually enough to determine how recently something has been changed.
`<pre>` tags have a default word wrap that causes words to break mid-word, which makes reading content difficult.
* Bump admin gem to pick up confirm JS module * Use module to warn when clicking publish or withdraw buttons and to confirm user action * Separate publish, withdraw and edit buttons to avoid accidental clicks * Always include a title on the “publish” container * Completely hide publish button when unavailable, a disabled button is confusing
* Some documents have a couple of attachments, others have hundreds * Always show the first 5 attachments * When more than 5 and when JS is enabled, hide the rest behind a toggle with a link that indicates how many more attachments will be revealed * Pattern pulled from Transition where it was well received for tables containing hundreds of mappings
Rather than hiding the entire `publish` pane, put it back with appropriate messaging. * Don’t mark the panel itself as dangerous, the publish action is red and that’s enough * Don’t give warnings when there are no changes or a user can’t publish * Use smart quotes in messaging
Clearly distinguish between editing, publishing and withdrawing. As withdrawing is the least used action it is at the bottom.
When something is withdrawn it is draft like, but not a draft. Instead indicate that the document can still be edited and published.
👍 This is great |
evilstreak
added a commit
that referenced
this pull request
Apr 10, 2015
Make UI more like other admin apps, prevent accidental publishing
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.
Supercedes #464 (force-pushed after master rebase so couldn't re-open old PR)
Differences with #464:
Original PR
confusing
show
pages with a consistent vertical rhythmlead
styles to make summary more readablegovuk_frontend_toolkit
– currently Bootstrap and the toolkit don’t play well togetherhttps://www.pivotaltracker.com/story/show/90529348
Editing a document
Before
After
Viewing a document
Before
Actions:
After
Actions:
Truncated attachments table
Warnings