-
Notifications
You must be signed in to change notification settings - Fork 19
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
layout on admin page not optimal #170
Comments
@VicDeo @jancborchardt can you help? |
I certainly agree to the suggestion! :-) I liked it better and if was much clearer and more organized, when updater opened up a separate page, where all items were shown complete and properly organized! regards, hitam4450 |
@te-online @VicDeo do you want to improve that here? The backups part should only be a h3 and no extra section div as to not separate it so much from the update part. |
Can take care of this over the weekend. Looking for some quick fixes. ;) |
Great stuff @raghunayyar – perfect to focus on the quick fixes for 8.2! :) |
@jancborchardt @raghunayyar Well, are you sure? I think I created this as an extra section, because it is an extra task. But proof me wrong 😉 |
@te-online it’s done by the same app, and apparently very related since one says »Updater-Backups«. ;) Hence it should be in the same section layout-wise. |
@jancborchardt If you say so 😉 |
@karlitschek It was me responsible for the ugly background 😄 @jancborchardt Call me too lazy to search, but you probably know it: Is there a go to place in the documentation that speaks about available formatting options for the interface? I'm always lost if things get more complicated than a heading and a paragraph. And obviously I don't want to introduce different stylings each time. |
Fixed by #171 – @raghunayyar good work! :) |
The layout of the updater app on the admin page is a bit over complicated and messy. It should be only one section and only show the information and buttons that are currently necessary.
Also the grey background is ugly. ;-)
The text was updated successfully, but these errors were encountered: