Docs: add info about textdomains to the package documentation #18070
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Changes proposed in this Pull Request:
Jetpack product discussion
We've been investigating providing a way for consumer plugins to change the textdomains in the packages. I found a couple of PRs from last year: #12525 and #12471. From the conversations in those PRs, in looks like the final decision was to let consumer plugins provide their own solution for updating textdomains in the packages.
I think this is the best approach. Consumer plugins should choose the tool and process that works best for that plugin, and there's no need for Jetpack to provide a tool for this. Instead, we should update the documentation so that consumer plugins understand that updating the textdomain is their responsibility. We can also provide links to a few tools that may be helpful, which I've done in this PR.
Does this pull request change what data or activity we track or use?
Testing instructions:
Proposed changelog entry for your changes: