No mention of KSES on Internationalization Security page

[johnbillion]

Issue Description

The Internationalization Security page makes no mention of KSES. It only covers translation escaping.

URL of the Page with the Issue

https://developer.wordpress.org/plugins/internationalization/security/

Section of Page with the issue

N/A

Why is this a problem?

Using KSES is a valuable way of allowing HTML in translations while maintaining security.

Suggested Fix

Add a section which documents the use of wp_kses() for allowing a trusted list of HTML tags and attributes for translations.

[github-actions]

Heads up @WordPress/docs-issues-coordinators, we have a new issue open. Time to use 'em labels.

[flexseth]

Greetings @johnbillion - I'm not sure this page actually ever existed in the plugin info. However- I am working on improving the plugin pages to include a sample plugin, security best practices, and how to best position a plugin developer to pass the check to allow their software to be offered in the WP.org plugin repo.

See that you have a couple of plugins that you've worked on, do you think you would be up to writing a simple section that explains

• Brief overview of KSES (can be copy/pasted from the security info, and linked there)
• How to use KSES in plugin development? Maybe some use cases using common hooks?

Even bringing some code in that you've written in one of your plugins would be helpful. We are looking for as many examples of what to do as possible for the various development handbooks!

Candidly, I haven't done much plugin development, mostly in the past I was a themer and now use JavaScript which I believe abstracts out the KSES functionality into the __() function from the i88n package. So I'm not really that great with plugin dev, but have been wanting to update this page in a big way.

You are right: The info should be there. Here's a Slack threadI started about mentioning security on the plugin best practices page...

Do you think you would be up to writing a brief blurb with some examples, and we can link out to the KSES section for more info?

Here's the current Best Practices for writing plugins page, I'd like to more highlight security here.

[flexseth]

/assign

[github-actions]

Hey @flexseth, thanks for your interest in this issue! 🍪🍪🍪
If you have any questions, do not hesitate to ask them in our #docs Slack channel.
Enjoy and happy contributing ❤️