[wp-trac] [WordPress Trac] #43715: Add Privacy Policy link to bundled theme footers

WordPress Trac noreply at wordpress.org
Sat Apr 28 00:10:47 UTC 2018


#43715: Add Privacy Policy link to bundled theme footers
-------------------------------------------------+-------------------------
 Reporter:  xkon                                 |       Owner:  xkon
     Type:  enhancement                          |      Status:  assigned
 Priority:  normal                               |   Milestone:  4.9.6
Component:  Bundled Theme                        |     Version:
 Severity:  normal                               |  Resolution:
 Keywords:  gdpr has-patch needs-testing needs-  |     Focuses:  ui, rtl
  dev-note                                       |
-------------------------------------------------+-------------------------

Comment (by iandunn):

 === Privacy Link Placement ===
 I played around w/ moving the privacy link outside of `site-info`, but
 that was worse than the current placement. I don't have any other ideas of
 how to mitigate the effects of custom CSS targeting `.site-info a` under
 the assumption that there's only 1 link, and no other elements.

 === Class for "Powered by..." Link ===

 [attachment:43715.8.diff] adds `class="imprint"` to all the `Proudly
 powered by WordPress` links, though, so that at least going forward people
 will be able to target both links individually.

 i'm not sure that "imprint" is the best term, but I spent an embarrassing
 amount of time trying to find a fancy, semantic publishing term that would
 fit, and that's the closest I came up with. I'm very open to any other
 suggestions.

 To kickstart brainstorming, here's some others I considered:
 * platform
 * generator
 * powered-by
 * powered-by-wordpress
 * shout-out

 === "Powered by..." formatting ===

 I also broke the "powered by..." links into multiple lines, because they
 were pretty long ''-- one was 266 characters! --'' and I find that very
 difficult to work with. I think that's kosher according to the guidelines
 and precendent, but let me know if anyone sees a reason to leave them like
 they were.

 === Next steps ===

 I think this is pretty close to being ready for commit. We can iterate
 some more on the above If anyone has any feedback or ideas, but if not
 then it might be at the point where we can commit it and see what comes up
 during beta testing.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/43715#comment:55>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform


More information about the wp-trac mailing list