WordPress.org

Making WordPress.org

Changeset 3419


Ignore:
Timestamp:
06/17/2016 06:47:28 PM (5 years ago)
Author:
obenland
Message:

Plugin Directory: More accurate styles for about pages.

See #1719.

Location:
sites/trunk/wordpress.org/public_html/wp-content/themes/pub/wporg-plugins
Files:
5 edited

Legend:

Unmodified
Added
Removed
  • sites/trunk/wordpress.org/public_html/wp-content/themes/pub/wporg-plugins/css/style-rtl.css

    r3418 r3419  
    22722272}
    22732273
    2274 .page .type-page {
    2275   margin: 0 auto;
    2276   max-width: 35.527136788rem;
    2277   padding: 0 2rem;
    2278 }
    2279 
    2280 .page h1 {
     2274.page .entry-header {
     2275  margin-top: 32px;
     2276  margin-top: 2rem;
     2277}
     2278
     2279.page .entry-header .entry-title {
    22812280  font-size: 25px;
    22822281  font-size: 1.5625rem;
    22832282  font-weight: 400;
    2284 }
    2285 
    2286 .page h2 {
     2283  margin: 0 auto;
     2284  max-width: 35.527136788rem;
     2285  padding: 0 32px;
     2286  padding: 0 2rem;
     2287}
     2288
     2289.page .entry-content h2 {
     2290  font-size: 25px;
     2291  font-size: 1.5625rem;
     2292  font-weight: 400;
     2293}
     2294
     2295.page .entry-content h3 {
    22872296  font-size: 16px;
    22882297  font-size: 1rem;
     
    22922301}
    22932302
    2294 .page hr {
    2295   margin-right: -6.5rem;
    2296   margin-left: -6.5rem;
     2303.page .entry-content section {
     2304  padding: 32px 0;
     2305  padding: 2rem 0;
     2306}
     2307
     2308.page .entry-content section .container {
     2309  margin: 0 auto;
     2310  max-width: 35.527136788rem;
     2311  padding: 0 32px;
     2312  padding: 0 2rem;
     2313}
     2314
     2315.page .entry-content section:first-of-type {
     2316  padding-top: 0;
     2317}
     2318
     2319.page .entry-content section + section {
     2320  border-top: 2px solid #eee;
    22972321}
    22982322
  • sites/trunk/wordpress.org/public_html/wp-content/themes/pub/wporg-plugins/css/style.css

    r3418 r3419  
    22722272}
    22732273
    2274 .page .type-page {
    2275   margin: 0 auto;
    2276   max-width: 35.527136788rem;
    2277   padding: 0 2rem;
    2278 }
    2279 
    2280 .page h1 {
     2274.page .entry-header {
     2275  margin-top: 32px;
     2276  margin-top: 2rem;
     2277}
     2278
     2279.page .entry-header .entry-title {
    22812280  font-size: 25px;
    22822281  font-size: 1.5625rem;
    22832282  font-weight: 400;
    2284 }
    2285 
    2286 .page h2 {
     2283  margin: 0 auto;
     2284  max-width: 35.527136788rem;
     2285  padding: 0 32px;
     2286  padding: 0 2rem;
     2287}
     2288
     2289.page .entry-content h2 {
     2290  font-size: 25px;
     2291  font-size: 1.5625rem;
     2292  font-weight: 400;
     2293}
     2294
     2295.page .entry-content h3 {
    22872296  font-size: 16px;
    22882297  font-size: 1rem;
     
    22922301}
    22932302
    2294 .page hr {
    2295   margin-left: -6.5rem;
    2296   margin-right: -6.5rem;
     2303.page .entry-content section {
     2304  padding: 32px 0;
     2305  padding: 2rem 0;
     2306}
     2307
     2308.page .entry-content section .container {
     2309  margin: 0 auto;
     2310  max-width: 35.527136788rem;
     2311  padding: 0 32px;
     2312  padding: 0 2rem;
     2313}
     2314
     2315.page .entry-content section:first-of-type {
     2316  padding-top: 0;
     2317}
     2318
     2319.page .entry-content section + section {
     2320  border-top: 2px solid #eee;
    22972321}
    22982322
  • sites/trunk/wordpress.org/public_html/wp-content/themes/pub/wporg-plugins/page-about.php

    r3374 r3419  
    2020
    2121            <div class="entry-content">
    22                 <p><?php printf( __( 'You’ve got a cool new plugin and are hoping to give it some exposure. You’re in the right place. Just <a href="%s">ask us to host it for you</a>. You’ll be able to:', 'wporg-plugins' ), esc_url( home_url( 'about/add' ) ) ); ?></p>
    23                 <ul>
    24                     <li><?php _e( 'Keep track of how many people have downloaded it.', 'wporg-plugins' ); ?></li>
    25                     <li><?php _e( 'Let people leave comments about your plugin.', 'wporg-plugins' ); ?></li>
    26                     <li><?php _e( 'Get your plugin rated against all the other cool WordPress plugins.', 'wporg-plugins' ); ?></li>
    27                     <li><?php _e( 'Give your plugin lots of exposure in this centralized repository.', 'wporg-plugins' ); ?></li>
    28                 </ul>
     22                <section>
     23                    <div class="container">
     24                        <p><?php printf( __( 'You’ve got a cool new plugin and are hoping to give it some exposure. You’re in the right place. Just <a href="%s">ask us to host it for you</a>. You’ll be able to:', 'wporg-plugins' ), esc_url( home_url( 'about/add' ) ) ); ?></p>
     25                        <ul>
     26                            <li><?php _e( 'Keep track of how many people have downloaded it.', 'wporg-plugins' ); ?></li>
     27                            <li><?php _e( 'Let people leave comments about your plugin.', 'wporg-plugins' ); ?></li>
     28                            <li><?php _e( 'Get your plugin rated against all the other cool WordPress plugins.', 'wporg-plugins' ); ?></li>
     29                            <li><?php _e( 'Give your plugin lots of exposure in this centralized repository.', 'wporg-plugins' ); ?></li>
     30                        </ul>
    2931
    30                 <h3><?php _e( 'There are some restrictions', 'wporg-plugins' ); ?></h3>
    31                 <ul>
    32                     <li><?php printf( __( 'Your plugin must be compatible with the <a href="%s">GNU General Public License v2</a>, or any later version. We strongly recommend using the same license as WordPress — “GPLv2 or later.” (If you don’t specify a compatible license, what you check in will considered GPLv2 or later.)', 'wporg-plugins' ), esc_url( 'http://www.gnu.org/licenses/license-list.html#GPLCompatibleLicenses' ) ); ?></li>
    33                     <li><?php _e( 'The plugin must not do anything illegal or be morally offensive (that’s subjective, we know).', 'wporg-plugins' ); ?></li>
    34                     <li><?php printf( __( 'You have to actually use the <a href="%s">Subversion</a> repository we give you in order for your plugin to show up on this site. The WordPress Plugin Directory is a hosting site, not a listing site.', 'wporg-plugins' ), esc_url( 'http://subversion.tigris.org/' ) ); ?></li>
    35                     <li><?php _e( 'The plugin must not embed external links on the public site (like a “powered by” link) without explicitly asking the user’s permission.', 'wporg-plugins' ); ?></li>
    36                     <li><?php printf( __( 'Your plugin must abide by our list of <a href="%s">detailed guidelines</a>, which include not being a spammer and not abusing the systems.', 'wporg-plugins' ), esc_url( 'https://developer.wordpress.org/plugins/wordpress-org/detailed-plugin-guidelines/' ) ); ?></li>
    37                 </ul>
     32                        <h3><?php _e( 'There are some restrictions', 'wporg-plugins' ); ?></h3>
     33                        <ul>
     34                            <li><?php printf( __( 'Your plugin must be compatible with the <a href="%s">GNU General Public License v2</a>, or any later version. We strongly recommend using the same license as WordPress — “GPLv2 or later.” (If you don’t specify a compatible license, what you check in will considered GPLv2 or later.)', 'wporg-plugins' ), esc_url( 'http://www.gnu.org/licenses/license-list.html#GPLCompatibleLicenses' ) ); ?></li>
     35                            <li><?php _e( 'The plugin must not do anything illegal or be morally offensive (that’s subjective, we know).', 'wporg-plugins' ); ?></li>
     36                            <li><?php printf( __( 'You have to actually use the <a href="%s">Subversion</a> repository we give you in order for your plugin to show up on this site. The WordPress Plugin Directory is a hosting site, not a listing site.', 'wporg-plugins' ), esc_url( 'http://subversion.tigris.org/' ) ); ?></li>
     37                            <li><?php _e( 'The plugin must not embed external links on the public site (like a “powered by” link) without explicitly asking the user’s permission.', 'wporg-plugins' ); ?></li>
     38                            <li><?php printf( __( 'Your plugin must abide by our list of <a href="%s">detailed guidelines</a>, which include not being a spammer and not abusing the systems.', 'wporg-plugins' ), esc_url( 'https://developer.wordpress.org/plugins/wordpress-org/detailed-plugin-guidelines/' ) ); ?></li>
     39                        </ul>
    3840
    39                 <h3><?php _e( 'Submission is Simple', 'wporg-plugins' ); ?></h3>
    40                 <ol>
    41                     <li><?php printf( __( '<a href="%s">Sign up</a> for an account on WordPress.org.', 'wporg-plugins' ), esc_url( 'https://wordpress.org/support/register.php' ) ); ?></li>
    42                     <li><?php printf( __( '<a href="%s">Submit your plugin for review</a>.', 'wporg-plugins' ), esc_url( home_url( 'about/add' ) ) ); ?></li>
    43                     <li><?php printf( __( 'After your plugin is <a href="%s">manually reviewed</a>, you will either be approved or emailed and asked to provide more information and/or make corrections.', 'wporg-plugins' ), esc_url( 'https://developer.wordpress.org/plugins/wordpress-org/plugin-developer-faq/#questions-about-submissions-and-approval' ) ); ?></li>
    44                     <li><?php printf( __( 'Once approved, you’ll be given access to a <a id="subversion" href="%s">Subversion Repository</a> where you’ll store your plugin.', 'wporg-plugins' ), esc_url( 'https://developer.wordpress.org/plugins/wordpress-org/how-to-use-subversion/' ) ); ?></li>
     41                        <h3><?php _e( 'Submission is Simple', 'wporg-plugins' ); ?></h3>
     42                        <ol>
     43                            <li><?php printf( __( '<a href="%s">Sign up</a> for an account on WordPress.org.', 'wporg-plugins' ), esc_url( 'https://wordpress.org/support/register.php' ) ); ?></li>
     44                            <li><?php printf( __( '<a href="%s">Submit your plugin for review</a>.', 'wporg-plugins' ), esc_url( home_url( 'about/add' ) ) ); ?></li>
     45                            <li><?php printf( __( 'After your plugin is <a href="%s">manually reviewed</a>, you will either be approved or emailed and asked to provide more information and/or make corrections.', 'wporg-plugins' ), esc_url( 'https://developer.wordpress.org/plugins/wordpress-org/plugin-developer-faq/#questions-about-submissions-and-approval' ) ); ?></li>
     46                            <li><?php printf( __( 'Once approved, you’ll be given access to a <a id="subversion" href="%s">Subversion Repository</a> where you’ll store your plugin.', 'wporg-plugins' ), esc_url( 'https://developer.wordpress.org/plugins/wordpress-org/how-to-use-subversion/' ) ); ?></li>
    4547
    46                     <li>
    47                         <?php
    48                         /* translators: 1: URL to readme section; 2: URL to home page; */
    49                         printf( __( 'Shortly after you upload your plugin (and a <a href="%1$s">readme file</a>!) to that repository, it will be automatically displayed in the <a href="%2$s">plugins browser</a>.', 'wporg-plugins' ), '#readme', esc_url( home_url( '/' ) ) );
    50                         ?>
    51                     </li>
    52                     <li><?php printf( __( 'Check out the <strong><a href="%s">FAQ</a> </strong>for more information.', 'wporg-plugins' ), esc_url( 'https://developer.wordpress.org/plugins/wordpress-org/plugin-developer-faq/' ) ); ?></li>
    53                 </ol>
     48                            <li>
     49                                <?php
     50                                /* translators: 1: URL to readme section; 2: URL to home page; */
     51                                printf( __( 'Shortly after you upload your plugin (and a <a href="%1$s">readme file</a>!) to that repository, it will be automatically displayed in the <a href="%2$s">plugins browser</a>.', 'wporg-plugins' ), '#readme', esc_url( home_url( '/' ) ) );
     52                                ?>
     53                            </li>
     54                            <li><?php printf( __( 'Check out the <strong><a href="%s">FAQ</a> </strong>for more information.', 'wporg-plugins' ), esc_url( 'https://developer.wordpress.org/plugins/wordpress-org/plugin-developer-faq/' ) ); ?></li>
     55                        </ol>
    5456
    55                 <h3 id="readme"><?php _e( 'Readme files', 'wporg-plugins' ); ?></h3>
    56                 <p>
    57                     <?php
    58                     /* translators: 1: URL to readme file; 2: URL to readme validator; */
    59                     printf( __( 'To make your entry in the plugin browser most useful, each plugin should have a readme file named <code>readme.txt</code> that adheres to the <a href="%1$s">WordPress plugin readme file standard</a>. You can put your readme file through the <a href="%2$s">readme validator</a> to check it.', 'wporg-plugins' ), esc_url( 'https://wordpress.org/plugins/files/2016/06/readme.txt' ), esc_url( 'https://wordpress.org/plugins/wp-admin/edit.php?post_type=plugin&page=readme_validator' ) );
    60                     ?>
    61                 </p>
     57                        <h3 id="readme"><?php _e( 'Readme files', 'wporg-plugins' ); ?></h3>
     58                        <p>
     59                            <?php
     60                            /* translators: 1: URL to readme file; 2: URL to readme validator; */
     61                            printf( __( 'To make your entry in the plugin browser most useful, each plugin should have a readme file named <code>readme.txt</code> that adheres to the <a href="%1$s">WordPress plugin readme file standard</a>. You can put your readme file through the <a href="%2$s">readme validator</a> to check it.', 'wporg-plugins' ), esc_url( 'https://wordpress.org/plugins/files/2016/06/readme.txt' ), esc_url( 'https://wordpress.org/plugins/wp-admin/edit.php?post_type=plugin&page=readme_validator' ) );
     62                            ?>
     63                        </p>
     64                    </div>
     65                </section>
    6266            </div><!-- .entry-content -->
    6367
  • sites/trunk/wordpress.org/public_html/wp-content/themes/pub/wporg-plugins/page-add.php

    r3374 r3419  
    2020
    2121            <div class="entry-content">
    22                 <p><?php printf( __( 'Once submitted, your plugin will be manually reviewed for any common errors as well as ensuring it complies with <a href="%s">all the guidelines</a>.', 'wporg-plugins' ), esc_url( 'https://developer.wordpress.org/plugins/wordpress-org/detailed-plugin-guidelines/' ) ); ?></p>
     22                <section>
     23                    <div class="container">
     24                        <p><?php printf( __( 'Once submitted, your plugin will be manually reviewed for any common errors as well as ensuring it complies with <a href="%s">all the guidelines</a>.', 'wporg-plugins' ), esc_url( 'https://developer.wordpress.org/plugins/wordpress-org/detailed-plugin-guidelines/' ) ); ?></p>
    2325
    24                 <?php do_shortcode( '[wporg-plugin-upload]' ); ?>
     26                        <?php echo do_shortcode( '[wporg-plugin-upload]' ); ?>
    2527
    26                 <p><?php _e( 'Even if you’ve submitted a dozen plugins, take the time to refresh your memory with the following information:', 'wporg-plugins' ); ?>
    27                 <ul>
    28                     <li><a href="https://developer.wordpress.org/plugins/wordpress-org/how-to-use-subversion/"><?php _e( 'How to use SVN', 'wporg-plugins' ); ?></a></li>
    29                     <li><a href="https://developer.wordpress.org/plugins/wordpress-org/deploying-your-plugin/"><?php _e( 'Deploying your plugin', 'wporg-plugins' ); ?></a></li>
    30                     <li><a href="https://developer.wordpress.org/plugins/wordpress-org/plugin-assets/"><?php _e( 'Plugin Assets (and how to use them)', 'wporg-plugins' ); ?></a></li>
    31                     <li><a href="https://developer.wordpress.org/plugins/wordpress-org/plugin-developer-faq/"><?php _e( 'Developer FAQ', 'wporg-plugins' ); ?></a></li>
    32                 </ul>
     28                        <p><?php _e( 'Even if you’ve submitted a dozen plugins, take the time to refresh your memory with the following information:', 'wporg-plugins' ); ?>
     29                        <ul>
     30                            <li><a href="https://developer.wordpress.org/plugins/wordpress-org/how-to-use-subversion/"><?php _e( 'How to use SVN', 'wporg-plugins' ); ?></a></li>
     31                            <li><a href="https://developer.wordpress.org/plugins/wordpress-org/deploying-your-plugin/"><?php _e( 'Deploying your plugin', 'wporg-plugins' ); ?></a></li>
     32                            <li><a href="https://developer.wordpress.org/plugins/wordpress-org/plugin-assets/"><?php _e( 'Plugin Assets (and how to use them)', 'wporg-plugins' ); ?></a></li>
     33                            <li><a href="https://developer.wordpress.org/plugins/wordpress-org/plugin-developer-faq/"><?php _e( 'Developer FAQ', 'wporg-plugins' ); ?></a></li>
     34                        </ul>
     35                    </div>
     36                </section>
    3337
    34                 <hr />
     38                <section>
     39                    <div class="container">
     40                        <h2 id="faq"><?php _e( 'FAQ', 'wporg-plugins' ); ?></h2>
    3541
    36                 <h3 id="faq"><?php _e( 'FAQ', 'wporg-plugins' ); ?></h3>
     42                        <h3><?php _e( 'How long will the review process take?', 'wporg-plugins' ); ?></h3>
     43                        <p><?php printf( __( 'This is in the <a href="%s">Developer FAQ</a>. It takes anywhere between 1 and 10 days. We attempt to review all plugins within 5 business days of submission, but the process takes as long as it takes, depending on the complexity of your plugin.', 'wporg-plugins' ), esc_url( 'https://developer.wordpress.org/plugins/wordpress-org/plugin-developer-faq/' ) ); ?></p>
    3744
    38                 <h4><?php _e( 'How long will the review process take?', 'wporg-plugins' ); ?></h4>
    39                 <p><?php printf( __( 'This is in the <a href="%s">Developer FAQ</a>. It takes anywhere between 1 and 10 days. We attempt to review all plugins within 5 business days of submission, but the process takes as long as it takes, depending on the complexity of your plugin.', 'wporg-plugins' ), esc_url( 'https://developer.wordpress.org/plugins/wordpress-org/plugin-developer-faq/' ) ); ?></p>
     45                        <h3><?php _e( 'What will my plugin URL be?', 'wporg-plugins' ); ?></h3>
     46                        <p><?php _e( 'Your plugin’s URL will be populated based on the value of <code>Plugin Name</code> in your main plugin file (the one with the plugin headers). If you set yours as <code>Plugin Name: Boaty McBoatface</code> then your URL will be <code>https://wordpress.org/plugins/boaty-mcboatface</code> and your slug will be <code>boaty-mcboatface</code> for example. If there is an existing plugin with your name, then you will be <code>boaty-mcboatface-2</code> and so on. It behaves exactly like WordPress post names.', 'wporg-plugins' ); ?></p>
     47                        <p><?php _e( 'Once your plugin is approved, it <em>cannot</em> be renamed.', 'wporg-plugins' ); ?></p>
    4048
    41                 <h4><?php _e( 'What will my plugin URL be?', 'wporg-plugins' ); ?></h4>
    42                 <p><?php _e( 'Your plugin’s URL will be populated based on the value of <code>Plugin Name</code> in your main plugin file (the one with the plugin headers). If you set yours as <code>Plugin Name: Boaty McBoatface</code> then your URL will be <code>https://wordpress.org/plugins/boaty-mcboatface</code> and your slug will be <code>boaty-mcboatface</code> for example. If there is an existing plugin with your name, then you will be <code>boaty-mcboatface-2</code> and so on. It behaves exactly like WordPress post names.', 'wporg-plugins' ); ?></p>
    43                 <p><?php _e( 'Once your plugin is approved, it <em>cannot</em> be renamed.', 'wporg-plugins' ); ?></p>
     49                        <h3><?php _e( 'I made a mistake in my plugin name. Should I resubmit?', 'wporg-plugins' ); ?></h3>
     50                        <p><?php _e( 'Please don’t! Instead email <code>plugins@wordpress.org</code> and we can rename your plugin as long as it’s not approved. Since we check emails first, the odds are we’ll catch it. If we don’t, just email us and explain the mistake. We’ll explain what do to.', 'wporg-plugins' ); ?></p>
    4451
    45                 <h4><?php _e( 'I made a mistake in my plugin name. Should I resubmit?', 'wporg-plugins' ); ?></h4>
    46                 <p><?php _e( 'Please don’t! Instead email <code>plugins@wordpress.org</code> and we can rename your plugin as long as it’s not approved. Since we check emails first, the odds are we’ll catch it. If we don’t, just email us and explain the mistake. We’ll explain what do to.', 'wporg-plugins' ); ?></p>
    47 
    48                 <h4><?php _e( 'Why was I told my plugin name was unacceptable?', 'wporg-plugins' ); ?></h4>
    49                 <p><?php printf( __( 'This is explained in detail in our <a href="%s">detailed plugin guidelines</a>, but currently we give you the chance to rename it during the review process if the plugin name violates the guideline. Some terms (like “plugin” and “wordpress”) will be removed for you, as those should not be used at all. We get it; you’re a WordPress Plugin.', 'wporg-plugins' ), esc_url( 'https://developer.wordpress.org/plugins/wordpress-org/detailed-plugin-guidelines/' ) ); ?></p>
    50                 <p><?php _e( 'Regarding the names and trademarks of other companies and plugins, don’t use them at the start of your plugin name. If you’re not Facebook, you shouldn’t submit a plugin that uses <code>facebook</code> as the first term in your slug. “Facebook Like Sharer” (which would be <code>facebook-like-sharer</code>) is not acceptable, but “Like Sharer for Facebook” (which would be <code>like-sharer-for-facebook</code>) would be alright.', 'wporg-plugins' ); ?></p>
     52                        <h3><?php _e( 'Why was I told my plugin name was unacceptable?', 'wporg-plugins' ); ?></h3>
     53                        <p><?php printf( __( 'This is explained in detail in our <a href="%s">detailed plugin guidelines</a>, but currently we give you the chance to rename it during the review process if the plugin name violates the guideline. Some terms (like “plugin” and “wordpress”) will be removed for you, as those should not be used at all. We get it; you’re a WordPress Plugin.', 'wporg-plugins' ), esc_url( 'https://developer.wordpress.org/plugins/wordpress-org/detailed-plugin-guidelines/' ) ); ?></p>
     54                        <p><?php _e( 'Regarding the names and trademarks of other companies and plugins, don’t use them at the start of your plugin name. If you’re not Facebook, you shouldn’t submit a plugin that uses <code>facebook</code> as the first term in your slug. “Facebook Like Sharer” (which would be <code>facebook-like-sharer</code>) is not acceptable, but “Like Sharer for Facebook” (which would be <code>like-sharer-for-facebook</code>) would be alright.', 'wporg-plugins' ); ?></p>
     55                    </div>
     56                </section>
    5157            </div><!-- .entry-content -->
    5258
  • sites/trunk/wordpress.org/public_html/wp-content/themes/pub/wporg-plugins/sass/site/primary/_page.scss

    r3398 r3419  
    22
    33.page {
    4     .type-page {
    5         margin: 0 auto;
    6         max-width: ms(32);
    7         padding: 0 2rem;
     4    .entry-header {
     5        margin-top: 32px;
     6        margin-top: 2rem;
     7
     8        .entry-title {
     9            @include font-size(ms-unitless(ms(4)));
     10            font-weight: 400;
     11            margin: 0 auto;
     12            max-width: ms(32);
     13            padding: 0 32px;
     14            padding: 0 2rem;
     15        }
    816    }
    917
    10     h1 {
    11         @include font-size( ms-unitless( ms(4) ) );
    12         font-weight: 400;
    13     }
    1418
    15     h2 {
    16         @include font-size( ms-unitless( ms(0) ) );
    17         font-weight: 600;
    18         letter-spacing: 0.01rem;
    19         text-transform: uppercase;
    20     }
     19    .entry-content {
     20        h2 {
     21            @include font-size(ms-unitless(ms(4)));
     22            font-weight: 400;
     23        }
    2124
    22     hr {
    23         margin-left: -6.5rem;
    24         margin-right: -6.5rem;
     25        h3 {
     26            @include font-size(ms-unitless(ms(0)));
     27            font-weight: 600;
     28            letter-spacing: 0.01rem;
     29            text-transform: uppercase;
     30        }
     31
     32        section {
     33            padding: 32px 0;
     34            padding: 2rem 0;
     35
     36            .container {
     37                margin: 0 auto;
     38                max-width: ms(32);
     39                padding: 0 32px;
     40                padding: 0 2rem;
     41            }
     42
     43            &:first-of-type {
     44                padding-top: 0;
     45            }
     46
     47            & + section {
     48                border-top: 2px solid $color__background-hr;
     49            }
     50        }
    2551    }
    2652}
Note: See TracChangeset for help on using the changeset viewer.