[wp-trac] [WordPress Trac] #43981: Privacy notices page: improve UX and readability

[WordPress Trac]

#43981: Privacy notices page: improve UX and readability
--------------------------+------------------------
 Reporter:  idea15        |       Owner:  (none)
     Type:  defect (bug)  |      Status:  closed
 Priority:  normal        |   Milestone:
Component:  General       |     Version:
 Severity:  normal        |  Resolution:  duplicate
 Keywords:  gdpr          |     Focuses:
--------------------------+------------------------

Comment (by danieliser):

 Replying to [comment:5 azaozz]:
 > Replying to [comment:3 danieliser]:
 > > 2. Edit page where there will be some noticeable button to generate
 policy text.
 > > 3. Show modal with tabbed form and ask relevant questions. (allow
 plugins to define extra questions, like are you using our subscription
 forms)
 > > 4. Generates text based on answers to questions and plugins installed.
 >
 > Like a "wizard" interface? Not sure if that will work. We cannot
 "generate" a privacy policy even if plugins output their bits of text in a
 structured form. It will be grammatically wrong as the different bits
 won't "fit" together, but more importantly this is improper from legal
 point of view. The site owners should be responsible for their policies,
 there is no way a policy can be auto-generated.

 To be clear, I completely agree, but you don't think most will leave what
 you have there now as the default?

 But once you factor in the average user you need to consider that the
 current solution offers the same end result in terms of what the user
 should be doing with it, that is they NEED to customize it. But the method
 I proposed means that it won't include unneeded info (if they don't check
 any analytics for instance, can skip that section). It also means that
 instead of 20 boxes of notes from Core and 19 other plugins they have
 installed, you get one box, one of each sections with all the info from
 all 19 plugins rolled in where it belongs (cookie info with core comment
 cookie note etc).

 So basically even though both solutions require customization by the admin
 in the end, the current solution means 20x the work on the average site as
 you merge the info from each plugin into your policy one by one, and my
 proposed solution means you only have to do it once and the options you
 chose can be saved for reuse the next time you generate the policy.

 Then factor in revision history vs newly generated and the user can at
 least reasonably get through updates in minutes, only having to invest a
 lot of time on the first version and easily able to merge changes from the
 old to new each time updates are needed.

 This would also easily lend itself to automatic timestamping of when the
 privacy policy was last updated.

 I just think the current solution is trying to get something out so
 quickly we are skipping how it will be used. I'm all for rushing something
 out to beat the deadline for site owners, but if we stick to what is here
 now, I fear nobody will make the deadline simply due to the sheer time it
 will take and the massive intimidation factor of the current
 implementation.

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