WordPress.org

Make WordPress Core

Opened 22 months ago

Last modified 21 months ago

#43620 closed enhancement

Privacy Policy page design — at Version 7

Reported by: melchoyce Owned by:
Milestone: 4.9.6 Priority: normal
Severity: normal Version:
Component: Privacy Keywords: gdpr has-patch needs-testing
Focuses: ui, administration Cc:
PR Number:

Description (last modified by ocean90)

Related to #43491 and #43473, this ticket addresses the design of the Privacy Policy page.

This design is a riff off of ticket:43435:edit-privacy-policy-page.png.

The draft has three main pieces:

  • Plugin Policies:
    • This is a collapsible box that lives above the Editor.
    • The header is styled like a warning notice, to attract attention to the text. The header contains an explanation of what the box contains and what you're supposed to do with it.
    • Each plugin providing a privacy policy will have a blurb and a "copy" button.
    • Question: Should the copy button copy text to the editor (I'd relabel it to "add to page page" or something), or just to your clipboard?
    • Question: Should there be some way to collapse or hide individual plugin blurbs?
  • Core Policies:
    • Core policies are automatically inserted into the page content.
    • Question: Do we see us making changes to this text between the first GDPR release, and when Gutenberg is released?
  • Confirmation:
    • This is inspired by the "Are you sure, [Author]?" confirmation the wordpress.org/news posts have.
    • The point of this extra step is to encourage people to review their privacy policy before publishing it.
    • When you check the box, the Publish button goes from disabled to enabled.
    • Question: Is this overkill?

Please note that none of the UI copy is final.

Change History (10)

#1 follow-up: @allendav
22 months ago

Thank you @melchoyce ! At the top of the mockup you say “reviewing… making any necessary edits… and then copying and pasting” - where will the user edit? (The order suggests the suggested policies meta box allows for editing _before_ it is copied and pasted.)

#2 @allendav
22 months ago

Also, it might be possible for us to determine internally when a plugin has provided a change for their suggested policy. For the initial implementation, it might be helpful to display a "Updated on {DATE}" in the context of a plugin's row - what do you think @melchoyce ?

(Down the road we could get fancy and do diffs or something, but I think all we need to do for the initial implementation is note when the suggested policy for a plugin last changed.)

#3 in reply to: ↑ 1 @melchoyce
22 months ago

Replying to allendav:

At the top of the mockup you say “reviewing… making any necessary edits… and then copying and pasting” - where will the user edit? (The order suggests the suggested policies meta box allows for editing _before_ it is copied and pasted.)

I'd expect users to make edits after pasting into the editor, so we'll want to update the copy to make this more clear.

Also, it might be possible for us to determine internally when a plugin has provided a change for their suggested policy. For the initial implementation, it might be helpful to display a "Updated on {DATE}" in the context of a plugin's row - what do you think @melchoyce ?

Yeah, let me try mocking this up.

#4 follow-up: @melchoyce
22 months ago

Okay, two ideas:

I think the first version would be more informative, but if it's not feasible, the second solution would work okay.

#5 in reply to: ↑ 4 @dejliglama
22 months ago

Replying to melchoyce:

Okay, two ideas:

You are right, this would be the best approach since texts are copied and then (probably) changed to fit the language and style of the Website owner. Making it good to put emphasis on changes to plugin and WP core policy texts.

#6 @dejliglama
22 months ago

The height of each of the policy text bites from plugins could probably vary greatly in length.
I would probably be a good idea to have a "read more" or "see full text" button.

The copy btn should, of course, copy the full-length text.

#7 @ocean90
22 months ago

  • Description modified (diff)
Note: See TracTickets for help on using tickets.