chuckya/app/views/layouts/admin.html.haml

- content_for :header_tags do
  = render_initial_state

- content_for :content do
  .admin-wrapper
    .sidebar-wrapper
      .sidebar-wrapper__inner
        .sidebar
          = link_to root_path do
            = render_logo

          .sidebar__toggle
            .sidebar__toggle__logo
              = link_to root_path do
                = logo_as_symbol(:wordmark)

            = link_to '#', class: 'sidebar__toggle__icon' do
              = fa_icon 'bars'

          = render_navigation

    .content-wrapper
      .content
        .content-heading
          - if content_for?(:heading)
            = yield :heading
          - else
            %h2= yield :page_title

          - if :heading_actions
            .content-heading-actions
              = yield :heading_actions

        = render 'application/flashes'

        = yield

    .sidebar-wrapper.sidebar-wrapper--empty

= render template: 'layouts/application'
Fix admin UI not loading JS, make sure to strip "acct:" out of remote account's usernames when authorizing follow 2017-01-03 06:31:10 +09:00			`- content_for :header_tags do`
Change reported media attachments to always be hidden in admin UI (#12879) Also: - Fix Mastodon logo not showing up in status embeds - Fix blurhash not being used in status embeds - Fix blurhash not being used in admin UI - Fix autoplay param not working correctly on status embeds 2020-01-19 03:50:43 +09:00			`= render_initial_state`
Update settings to re-use admin layout, one big navigation tree, improve settings forms 2017-01-28 11:56:10 +09:00
Improved admin UI 2016-12-13 21:42:10 +09:00			`- content_for :content do`
			`.admin-wrapper`
Update settings to re-use admin layout, one big navigation tree, improve settings forms 2017-01-28 11:56:10 +09:00			`.sidebar-wrapper`
Fix page body not being scrollable in admin layout (#11893) Hide navigation behind hamburger icon on small screens in admin layout 2019-09-20 17:52:14 +09:00			`.sidebar-wrapper__inner`
			`.sidebar`
			`= link_to root_path do`
Change brand color and logotypes (#18592) - Add rake task for generating Apple/Android icons and favicons from SVG - Add rake task for generating PNG icons and logos for e-mails from SVG - Remove obsolete Microsoft icons and configuration - Remove PWA shortcut icons 2022-06-10 05:25:23 +09:00			`= render_logo`
Fix page body not being scrollable in admin layout (#11893) Hide navigation behind hamburger icon on small screens in admin layout 2019-09-20 17:52:14 +09:00
			`.sidebar__toggle`
			`.sidebar__toggle__logo`
			`= link_to root_path do`
Change brand color and logotypes (#18592) - Add rake task for generating Apple/Android icons and favicons from SVG - Add rake task for generating PNG icons and logos for e-mails from SVG - Remove obsolete Microsoft icons and configuration - Remove PWA shortcut icons 2022-06-10 05:25:23 +09:00			`= logo_as_symbol(:wordmark)`
Fix page body not being scrollable in admin layout (#11893) Hide navigation behind hamburger icon on small screens in admin layout 2019-09-20 17:52:14 +09:00
			`= link_to '#', class: 'sidebar__toggle__icon' do`
			`= fa_icon 'bars'`

			`= render_navigation`
Improved admin UI 2016-12-13 21:42:10 +09:00
Update settings to re-use admin layout, one big navigation tree, improve settings forms 2017-01-28 11:56:10 +09:00			`.content-wrapper`
			`.content`
Improve report page structure (#12615) * 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. 2019-12-17 07:55:16 +09:00			`.content-heading`
Add administrative webhooks (#18510) * Add administrative webhooks * Fix error when webhook is deleted before delivery worker runs 2022-06-10 04:57:36 +09:00			`- if content_for?(:heading)`
			`= yield :heading`
			`- else`
			`%h2= yield :page_title`
Improve report page structure (#12615) * 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. 2019-12-17 07:55:16 +09:00
Rename page_heading_actions variable (#12799) Current name - page_heading_actions is long and hard to remember, this commit shortens it to just heading_actions, which is way more easier to remember and write, it's logical too. 2020-01-10 09:10:17 +09:00			`- if :heading_actions`
Improve report page structure (#12615) * 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. 2019-12-17 07:55:16 +09:00			`.content-heading-actions`
Rename page_heading_actions variable (#12799) Current name - page_heading_actions is long and hard to remember, this commit shortens it to just heading_actions, which is way more easier to remember and write, it's logical too. 2020-01-10 09:10:17 +09:00			`= yield :heading_actions`
Import feature for following/blocking lists (addresses #62, #177, #201, #454) 2017-03-31 02:42:33 +09:00
Fix flashes partial render error for controllers which don't inherit from application controller (#2400) * Add failing spec for oauth/authorized_applications controller * Use explicit reference to flashes partial from admin layout Because some of the controllers which use the admin layout do not inherit from application controller, this partial is not in their view path. 2017-04-25 00:30:30 +09:00			`= render 'application/flashes'`
Import feature for following/blocking lists (addresses #62, #177, #201, #454) 2017-03-31 02:42:33 +09:00
Update settings to re-use admin layout, one big navigation tree, improve settings forms 2017-01-28 11:56:10 +09:00			`= yield`
Improved admin UI 2016-12-13 21:42:10 +09:00
Fix page body not being scrollable in admin layout (#11893) Hide navigation behind hamburger icon on small screens in admin layout 2019-09-20 17:52:14 +09:00			`.sidebar-wrapper.sidebar-wrapper--empty`

Set @body_classes to admin layout (#9081) 2018-10-25 07:10:01 +09:00			`= render template: 'layouts/application'`