docs: refresh wp.org readme copy and clean up changelog formatting - #1939
Merged
arifulhoque7 merged 1 commit intoAug 12, 2026
Merged
Conversation
Rewrite the plugin title, short description and Description body for the wp.org listing, and fix formatting the readme parser mishandled: - Demote "Why Choose User Frontend" and "Perfect for Building" from `==` to `=`; as top-level sections they were parsed as separate readme sections instead of Description subheadings. - Normalise inline bold to Markdown `**` (already used elsewhere in the file) and drop the stray empty `= =` heading. - Drop the `v` prefix from changelog version headings so they match the released version numbers. - Collapse the duplicated 4.0.1-4.0.3 and 4.2.8 changelog entries into re-release notes, and fix the escaped-emoji markup in the 4.1.8 entry. - Add the missing trailing newline. No functional changes.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Refreshes the wp.org listing copy (plugin title, short description, Description body) and fixes formatting the wp.org readme parser mishandles.
Changes
Why Choose User FrontendandPerfect for Buildingdemoted from==to=. As==they were parsed as separate top-level readme sections rather than Description subheadings.<strong>to Markdown**, matching the style already used in the Pro feature list.= =heading before Screenshots.vprefix (= v4.3.10 =→= 4.3.10 =) so headings match the released version numbers.shortcdoeandmain compatibilitytypos.Short description is 141 chars (under the 150 limit). No
##Markdown headers, no CRLF.Notes
readme.txtonly.trunk+tags/4.3.10) so the live listing updates without waiting for a release; the wp.org page servestags/<Stable tag>/readme.txt.