Changeset 6878 for sites/trunk/wordpress.org/public_html/wp-content/themes/pub/wporg-main/page-about-domains.php
- Timestamp:
- 03/15/2018 04:42:32 AM (7 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
sites/trunk/wordpress.org/public_html/wp-content/themes/pub/wporg-main/page-about-domains.php
r6869 r6878 36 36 <article id="post-<?php the_ID(); ?>" <?php post_class(); ?>> 37 37 <header class="entry-header"> 38 <h1 class="entry-title col-8"><?php _esc_html_e( 'Domains', 'wporg' ); ?></h1>38 <h1 class="entry-title col-8"><?php esc_html_e( 'Domains', 'wporg' ); ?></h1> 39 39 </header><!-- .entry-header --> 40 40 41 41 <div class="entry-content row"> 42 42 <section class="col-8"> 43 <p><?php echo wp_kses_post( __ _( 'For various reasons related to our WordPress trademark, we ask if you’re going to start a site about WordPress or related to it that you <strong>not</strong> use “WordPress” in the domain name. Try using “wp” instead, or another variation. We’re not lawyers, but very good ones tell us we have to do this to preserve our trademark. Also, many users have told us they find it confusing.', 'wporg' ) ); ?></p>43 <p><?php echo wp_kses_post( __( 'For various reasons related to our WordPress trademark, we ask if you’re going to start a site about WordPress or related to it that you <strong>not</strong> use “WordPress” in the domain name. Try using “wp” instead, or another variation. We’re not lawyers, but very good ones tell us we have to do this to preserve our trademark. Also, many users have told us they find it confusing.', 'wporg' ) ); ?></p> 44 44 45 <p><?php _esc_html_e( 'If you already have a domain with “WordPress” in it, redirecting it to the “wp” equivalent is fine, just as long as the main one users see and you promote doesn’t contain “WordPress” and in the long term you should consider transferring the old one to the Foundation.', 'wporg' ); ?></p>45 <p><?php esc_html_e( 'If you already have a domain with “WordPress” in it, redirecting it to the “wp” equivalent is fine, just as long as the main one users see and you promote doesn’t contain “WordPress” and in the long term you should consider transferring the old one to the Foundation.', 'wporg' ); ?></p> 46 46 47 47 <p> 48 48 <?php 49 echo wp_kses_post( __ _( '“WordPress” in sub-domains is fine, like <code>wordpress.example.com</code>, we’re just concerned about top-level domains.', 'wporg' ) ); // phpcs:ignore WordPress.WP.CapitalPDangit.Misspelled49 echo wp_kses_post( __( '“WordPress” in sub-domains is fine, like <code>wordpress.example.com</code>, we’re just concerned about top-level domains.', 'wporg' ) ); // phpcs:ignore WordPress.WP.CapitalPDangit.Misspelled 50 50 ?> 51 51 </p> 52 52 53 <p><?php _esc_html_e( 'We’ve told this to anyone who has ever asked us, we just wanted to make it public so more people could be aware of this policy.', 'wporg' ); ?></p>53 <p><?php esc_html_e( 'We’ve told this to anyone who has ever asked us, we just wanted to make it public so more people could be aware of this policy.', 'wporg' ); ?></p> 54 54 55 <p><strong><?php _esc_html_e( '<whine>Other domains are using WordPress in them!</whine>', 'wporg' ); ?></strong></p>56 <p><?php _esc_html_e( 'If they’re not WordPress.com, WordPress.net, WordPress.org, WordPress.tv, or WordPressFoundation.org, they’re not allowed, and you should contact the owner with a pointer to this page. We see this most frequently with spammy sites distributing plugins and themes with malware in them, which you probably don’t want to be associated with.', 'wporg' ); ?></p>55 <p><strong><?php esc_html_e( '<whine>Other domains are using WordPress in them!</whine>', 'wporg' ); ?></strong></p> 56 <p><?php esc_html_e( 'If they’re not WordPress.com, WordPress.net, WordPress.org, WordPress.tv, or WordPressFoundation.org, they’re not allowed, and you should contact the owner with a pointer to this page. We see this most frequently with spammy sites distributing plugins and themes with malware in them, which you probably don’t want to be associated with.', 'wporg' ); ?></p> 57 57 </section> 58 58 </div><!-- .entry-content -->
Note: See TracChangeset
for help on using the changeset viewer.