Localization POT about theme-scaffold HOT 3 OPEN

@ivanlopez What would this look like in practice? Is it something we can include on all projects or is it more conditional?

from theme-scaffold.

@ivanlopez @timwright12

I did some discovery on this today. Since this Issue was opened over a year ago a lot has changed, but not much at the same time 😄

It seems that WP-CLI (wp i18n) is the most practical means to generate POT files, and it covers PHP and JS. Whereas, there are other methods, but they take set up and either cover just JS (@wordpress/babel-plugin-makepot) or PHP.

I imagine that POT file generation for a project is something that is done later on in the build, and closer to the end. Automation is tricky. Probably not impossible, but current documentation is lacking.

I would think this is project specific and would surface as a conversation early on in the build if i18n is critical. I do not currently see it being something that would be practical, nor needed within the Theme Scaffold.

Resources:

• https://github.com/wp-cli/i18n-command
• https://www.smashingmagazine.com/2018/01/internationalize-your-wordpress-website/
• ahmadawais/create-guten-block#24 (comment)
• https://github.com/swissspidy/gutenberg-i18n-block
• https://pascalbirchler.com/internationalization-in-wordpress-5-0/
• https://wordpress.org/gutenberg/handbook/designers-developers/developers/internationalization/
• https://developer.wordpress.org/plugins/internationalization/how-to-internationalize-your-plugin/

from theme-scaffold.

I like the idea of using wp i18n here. Wondering if we can build this into the build-release NPM script? Or something similar? That we we don't have to worry about it every time. The other option, of course is to rather keep this out of the theme scaffold and rather include it in our deploy-scripts ? I'll defer to someone else for advice / insight there.

from theme-scaffold.