Add a privacy policy page setting/selector to the customizer

[allendav]

Adds a privacy policy page setting/selector to the customizer, leveraging the work done in #43435 to define a privacy policy page option.

[Clorith]

What benefit does this provide in adding it as more options to core?

The current home page and blog page options serve a code purpose, and a need. Adding a privacy page selector feels like adding an option for the sake of "looking like we care" more so than anything else?

[dejliglama]

@allendav so this ticket is "only" about choosing a page to "be" the policy page (from a dropdown, or other means of selection)?

And we need this - to be able to code the specific page element that @melchoyce in #43620 is designing into that specific page... Correct?

[allendav]

Replying to dejliglama:

@allendav so this ticket is "only" about choosing a page to "be" the policy page (from a dropdown, or other means of selection)?

yes

And we need this - to be able to code the specific page element that @melchoyce in #43620 is designing into that specific page... Correct?

not quite - we have added the setting to wp-admin recently (on trunk, look in Tools > Privacy) so you could use wp-admin to set the specific page, but...

to answer @Clorith 's question as well...

I am proposing adding this to the customizer so that it is not necessary for a site admin to use wp-admin to set this page, and because with the GDPR a Privacy Policy page is a must-have for anyone serving EU residents from their site (not just stores, but blogs as well)...

and... since the customizer is (supposed to be?) the preferred interface for appearance related items of which (i think?) this is an important one

[Clorith]

I'm still not sure I understand the need here, you would have to link to this page, meaning any old page would do that's linked to via the menu component in core. We can't inject the link automatically because verbiage might differ on the labeling of that link depending on language, and context.

[melchoyce]

Yeah, I'm not sure this is a good use-case for the Customizer. Just setting the page doesn't help much if there isn't anything else you can configure without hopping out and actually editing the page content.

[xkon]

I'd say as well let's leave the Customizer out of it, at least for the time being. Let's direct everything to 1 spot for the start as it'll already be pretty confusing to some. I understand the diversity and 'ease of use' to have everything accessible from various points but this is for something super specific and not for the general UI/UX of the front-end website as Customizer is usually.

[desrosj]

Moving to the new Privacy component.

[desrosj]

I agree that this does not seem like a good use of the Customizer right now. Marking maybelater as some new functionality may make this useful in the future.