34aa5c7cb2
* Move resolved button to the heading This is one of the commits on improving overall reports page structure. It changes where resolved button is located, moving it to the heading, right next to the "Report #n" header, so-called "hot-place" to look at. To accomplish this we have to declare one more content variable, change admin dashboard template to respect it and CSS files for minor styling, so buttons are inlined and centrally aligned according to the heading. * Move actions buttons below the report table I believe that actions to react on report should not be located at the top of the page, instead they should be either after the table or reporter's comment. This is just a logical sign that you should not react to the report without reading all the details first.
38 lines
937 B
Plaintext
38 lines
937 B
Plaintext
- content_for :header_tags do
|
|
= javascript_pack_tag 'public', integrity: true, crossorigin: 'anonymous'
|
|
|
|
- content_for :content do
|
|
.admin-wrapper
|
|
.sidebar-wrapper
|
|
.sidebar-wrapper__inner
|
|
.sidebar
|
|
= link_to root_path do
|
|
= image_pack_tag 'logo.svg', class: 'logo', alt: 'Mastodon'
|
|
|
|
.sidebar__toggle
|
|
.sidebar__toggle__logo
|
|
= link_to root_path do
|
|
= svg_logo_full
|
|
|
|
= link_to '#', class: 'sidebar__toggle__icon' do
|
|
= fa_icon 'bars'
|
|
|
|
= render_navigation
|
|
|
|
.content-wrapper
|
|
.content
|
|
.content-heading
|
|
%h2= yield :page_title
|
|
|
|
- if :page_heading_actions
|
|
.content-heading-actions
|
|
= yield :page_heading_actions
|
|
|
|
= render 'application/flashes'
|
|
|
|
= yield
|
|
|
|
.sidebar-wrapper.sidebar-wrapper--empty
|
|
|
|
= render template: 'layouts/application'
|