3.2.4 (Media Mark) 108226a14f745716eb0c551ba70bbd0a28af55dd o:Sass::Tree::RootNode :@children[ o:Sass::Tree::CommentNode : @value[I"K/* SASS variable overrides must be declared before loading up Active Admin's styles. * * To view the variables that Active Admin provides, take a look at * `app/assets/stylesheets/active_admin/mixins/_variables.css.scss` in the * Active Admin source. * * For example, to change the sidebar width: * $sidebar-width: 242px; */:ET: @type: silent;[: @linei: @options{o; ;[I"#/* Active Admin's got SASS! */; T; ; ;[; i; @ o:Sass::Tree::ImportNode :@imported_filenameI"active_admin/mixins; T;[:@template0; i; @ :@imported_file0o; ;I"active_admin/base; T;[;0; i; @ ;0o; ;[I"Ñ/* Overriding any non-variable SASS must be done after the fact. * For example, to change the default status-tag color: * * body.active_admin { * .status_tag { background: #6090DB; } * } * * Notice that Active Admin CSS rules are nested within a * 'body.active_admin' selector to prevent conflicts with * other pages in the app. It is best to wrap your changes in a * namespace so they are properly recognized. You have options * if you e.g. want different styles for different namespaces: * * .active_admin applies to any Active Admin namespace * .admin_namespace applies to the admin namespace (eg: /admin) * .other_namespace applies to a custom namespace named other (eg: /other) */; T; ; ;[; i; @ ;I"r// SASS variable overrides must be declared before loading up Active Admin's styles. // // To view the variables that Active Admin provides, take a look at // `app/assets/stylesheets/active_admin/mixins/_variables.css.scss` in the // Active Admin source. // // For example, to change the sidebar width: // $sidebar-width: 242px; // Active Admin's got SASS! @import "active_admin/mixins"; @import "active_admin/base"; // Overriding any non-variable SASS must be done after the fact. // For example, to change the default status-tag color: // // body.active_admin { // .status_tag { background: #6090DB; } // } // // Notice that Active Admin CSS rules are nested within a // 'body.active_admin' selector to prevent conflicts with // other pages in the app. It is best to wrap your changes in a // namespace so they are properly recognized. You have options // if you e.g. want different styles for different namespaces: // // .active_admin applies to any Active Admin namespace // .admin_namespace applies to the admin namespace (eg: /admin) // .other_namespace applies to a custom namespace named other (eg: /other) ; T; i:@has_childrenT; @