Making WordPress.org


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

Plugin Directory: More accurate styles for about pages.

See #1719.

File:
1 edited

Legend:

Unmodified
Added
Removed
  • 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
Note: See TracChangeset for help on using the changeset viewer.