Change feature "Traffic Boost" to "Engagement Boost" #3482
Merged
Conversation
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
Contributor
📝 Walkthrough## Walkthrough
All references to the "Traffic Boost" feature have been renamed to "Engagement Boost" across the codebase. This includes updates to UI text, menu labels, route paths, link URLs, accessibility labels, and user-facing messages. No changes were made to core logic, control flow, or exported entity declarations.
## Changes
| Files/Groups | Change Summary |
|------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------|
| src/UI/class-dashboard-page.php, src/UI/class-settings-page.php | Updated menu, page, and settings labels from "Traffic Boost" to "Engagement Boost". |
| src/UI/class-row-actions.php | Changed row action link label and URL from "Boost Traffic" to "Boost Engagement" and updated path segment. |
| src/content-helper/dashboard-page/dashboard-page.tsx | Renamed route paths from `/traffic-boost` to `/engagement-boost` and updated default redirect. |
| src/content-helper/dashboard-page/components/posts-table/components/single-post-row.tsx | Updated link path and text from "Boost Traffic" to "Boost Engagement". |
| src/content-helper/dashboard-page/components/posts-table/components/suggestion-bubble.tsx | Changed navigation target from `/traffic-boost/${postId}` to `/engagement-boost/${postId}`. |
| src/content-helper/dashboard-page/pages/dashboard/header-component.tsx | Changed StatCard title from "Traffic Boost" to "Engagement Boost". |
| src/content-helper/dashboard-page/pages/traffic-boost/page-component.tsx | Updated page header from "Manage Traffic Boost (beta)" to "Manage Engagement Boost (beta)". |
| src/content-helper/dashboard-page/pages/traffic-boost/sidebar/components/links-list/single-link.tsx | Changed aria-label from "Traffic boost link" to "Engagement boost link". |
| src/content-helper/dashboard-page/pages/traffic-boost/sidebar/components/post-details.tsx | Updated description from "increase your post's traffic" to "increase your post's engagement". |
| src/content-helper/dashboard-page/pages/traffic-boost/sidebar/components/tabs-content.tsx | Replaced "Traffic Boost" with "Engagement Boost" in error and link texts. |
| src/content-helper/dashboard-page/pages/traffic-boost/sidebar/sidebar.tsx | Changed sidebar back navigation from `/traffic-boost` to `/engagement-boost`. |
| src/content-helper/dashboard-page/pages/traffic-boost/single-post-component.tsx | Updated redirect path from `/traffic-boost` to `/engagement-boost` on missing post. |
| src/js/admin-settings.ts | Updated user-facing message from "Traffic Boost" to "Engagement Boost" in API authorization error. |
| README.md | Renamed "Traffic Boost" to "Engagement Boost" in descriptions and screenshots; cleaned whitespace. |
## Sequence Diagram(s)
```mermaid
sequenceDiagram
participant User
participant WP_Admin
participant React_Dashboard
User->>WP_Admin: Clicks "Engagement Boost" in menu
WP_Admin->>React_Dashboard: Loads /engagement-boost route
React_Dashboard->>User: Renders Engagement Boost UI
User->>React_Dashboard: Clicks "Boost Engagement" link for a post
React_Dashboard->>React_Dashboard: Navigates to /engagement-boost/:postId
React_Dashboard->>User: Shows Engagement Boost details for postPossibly related PRs
Suggested labels
Suggested reviewers
|
Contributor
There was a problem hiding this comment.
Actionable comments posted: 1
📜 Review details
Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
⛔ Files ignored due to path filters (4)
build/admin-settings.asset.phpis excluded by!build/**build/admin-settings.jsis excluded by!build/**build/content-helper/dashboard-page.asset.phpis excluded by!build/**build/content-helper/dashboard-page.jsis excluded by!build/**
📒 Files selected for processing (14)
src/UI/class-dashboard-page.php(1 hunks)src/UI/class-row-actions.php(2 hunks)src/UI/class-settings-page.php(1 hunks)src/content-helper/dashboard-page/components/posts-table/components/single-post-row.tsx(1 hunks)src/content-helper/dashboard-page/components/posts-table/components/suggestion-bubble.tsx(1 hunks)src/content-helper/dashboard-page/dashboard-page.tsx(1 hunks)src/content-helper/dashboard-page/pages/dashboard/header-component.tsx(1 hunks)src/content-helper/dashboard-page/pages/traffic-boost/page-component.tsx(1 hunks)src/content-helper/dashboard-page/pages/traffic-boost/sidebar/components/links-list/single-link.tsx(1 hunks)src/content-helper/dashboard-page/pages/traffic-boost/sidebar/components/post-details.tsx(1 hunks)src/content-helper/dashboard-page/pages/traffic-boost/sidebar/components/tabs-content.tsx(2 hunks)src/content-helper/dashboard-page/pages/traffic-boost/sidebar/sidebar.tsx(1 hunks)src/content-helper/dashboard-page/pages/traffic-boost/single-post-component.tsx(1 hunks)src/js/admin-settings.ts(1 hunks)
🧰 Additional context used
📓 Path-based instructions (2)
`**/*.{js,ts,tsx,jsx}`: "Perform a detailed review of the provided code with following key aspects in mind: - Review the code to ensure it is well-structured and adheres to best ...
**/*.{js,ts,tsx,jsx}: "Perform a detailed review of the provided code with following key aspects in mind:
- Review the code to ensure it is well-structured and adheres to best practices.
- Verify compliance with WordPress coding standards.
- Ensure the code is well-documented.
- Check for security vulnerabilities and confirm the code is secure.
- Optimize the code for performance, removing any unnecessary elements.
- Validate JSDoc comments for accuracy, currency, and adherence to WordPress coding standards.
- Ensure each line comment concludes with a period.
- Confirm every JSDoc comment includes a @SInCE tag indicating the next version of the plugin to include the code.
- Guarantee compatibility with the latest version of WordPress, avoiding deprecated functions or features."
src/content-helper/dashboard-page/pages/traffic-boost/sidebar/components/links-list/single-link.tsxsrc/js/admin-settings.tssrc/content-helper/dashboard-page/pages/dashboard/header-component.tsxsrc/content-helper/dashboard-page/components/posts-table/components/single-post-row.tsxsrc/content-helper/dashboard-page/components/posts-table/components/suggestion-bubble.tsxsrc/content-helper/dashboard-page/pages/traffic-boost/page-component.tsxsrc/content-helper/dashboard-page/pages/traffic-boost/sidebar/sidebar.tsxsrc/content-helper/dashboard-page/pages/traffic-boost/sidebar/components/post-details.tsxsrc/content-helper/dashboard-page/dashboard-page.tsxsrc/content-helper/dashboard-page/pages/traffic-boost/single-post-component.tsxsrc/content-helper/dashboard-page/pages/traffic-boost/sidebar/components/tabs-content.tsx
`**/*.{html,php}`: "Perform a detailed review of the provided code with following key aspects in mind: - Review the HTML and PHP code to ensure it is well-structured and adheres ...
**/*.{html,php}: "Perform a detailed review of the provided code with following key aspects in mind:
- Review the HTML and PHP code to ensure it is well-structured and adheres to best practices.
- Ensure the code follows WordPress coding standards and is well-documented.
- Confirm the code is secure and free from vulnerabilities.
- Optimize the code for performance, removing any unnecessary elements.
- Validate comments for accuracy, currency, and adherence to WordPress coding standards.
- Ensure each line comment concludes with a period.
- Verify code compatibility with the latest version of WordPress, avoiding deprecated functions or features."
src/UI/class-dashboard-page.phpsrc/UI/class-settings-page.phpsrc/UI/class-row-actions.php
⏰ Context from checks skipped due to timeout of 90000ms (2)
- GitHub Check: E2E against WordPress latest
- GitHub Check: build
🔇 Additional comments (16)
src/content-helper/dashboard-page/pages/traffic-boost/page-component.tsx (1)
32-32: Brand label update looks good
Public-facing copy correctly reflects the new feature name. No further changes required in this component.src/UI/class-dashboard-page.php (1)
186-188: Sub-menu text updated correctly
Labels and page titles align with the rebrand; no functional impact.src/content-helper/dashboard-page/pages/traffic-boost/sidebar/components/links-list/single-link.tsx (1)
79-80: Accessible label updated correctly
String is localised and keeps the existing translator comment structure.src/UI/class-settings-page.php (1)
518-523: Settings legend text updated correctly
Translation domain retained, no logic affected.src/content-helper/dashboard-page/pages/traffic-boost/sidebar/sidebar.tsx (1)
116-116: LGTM! Navigation path correctly updated to match feature renaming.The navigation path change from
/traffic-boostto/engagement-boostis consistent with the feature renaming objective.src/content-helper/dashboard-page/components/posts-table/components/single-post-row.tsx (2)
167-167: LGTM! Route path correctly updated.The pathname change from
/traffic-boost/${post.id}to/engagement-boost/${post.id}is consistent with the feature renaming.
173-173: LGTM! Link text properly updated with correct internationalization.The link text change from "Boost Traffic" to "Boost Engagement" maintains proper WordPress i18n usage and aligns with the feature renaming objective.
src/content-helper/dashboard-page/components/posts-table/components/suggestion-bubble.tsx (1)
40-40: LGTM! Navigation path correctly updated.The navigation path change from
/traffic-boost/${postId}to/engagement-boost/${postId}is consistent with the feature renaming objective.src/content-helper/dashboard-page/pages/traffic-boost/sidebar/components/post-details.tsx (1)
49-50: LGTM! User-facing text correctly updated to reflect engagement focus.The text change from "increase your post's traffic" to "increase your post's engagement" properly aligns with the feature renaming objective and maintains correct WordPress i18n usage.
src/content-helper/dashboard-page/pages/traffic-boost/single-post-component.tsx (1)
209-209: LGTM! Redirect path correctly updated.The navigation path change from
/traffic-boostto/engagement-boostmaintains the correct redirect behavior when no post is found, consistent with the feature renaming.src/js/admin-settings.ts (1)
286-286: LGTM! Clean terminology update.The error message has been correctly updated from "Traffic Boost" to "Engagement Boost" while maintaining proper escaping and internationalization. The change aligns perfectly with the feature renaming objectives.
src/UI/class-row-actions.php (2)
166-166: Correct URL path update.The admin URL has been properly updated from
/traffic-boost/to/engagement-boost/to align with the new route structure.
177-177: Proper link text update.The visible link text has been correctly updated from "Boost Traffic" to "Boost Engagement" while maintaining proper internationalization with
esc_html__().src/content-helper/dashboard-page/pages/traffic-boost/sidebar/components/tabs-content.tsx (2)
84-84: Consistent link text update.The hyperlink text has been correctly updated from "Traffic Boost" to "Engagement Boost" while maintaining proper internationalization.
97-97: Proper error message update.The error message has been correctly updated to reference "Engagement Boost" instead of "Traffic Boost" while preserving the sprintf placeholders and internationalization structure.
src/content-helper/dashboard-page/dashboard-page.tsx (1)
50-52: Consistent route structure updates.All three routing changes correctly update the paths from "traffic-boost" to "engagement-boost":
- Default redirect properly routes users to the new path
- Both main route and parameterized route are updated consistently
- Component references remain unchanged as intended per PR scope
The routing logic maintains its structure while reflecting the new terminology.
Contributor
There was a problem hiding this comment.
Actionable comments posted: 0
🧹 Nitpick comments (2)
README.md (2)
9-9: Consider adding the new keyword to the plugin “Tags” listNow that the public-facing feature is called “Engagement Boost”, it may be worth expanding the tag list to include
engagementso the plugin is still easily discoverable in searches.
120-121: Screenshot caption updated, underlying asset still genericThe caption now references “Engagement Boost” yet the image filename remains
screenshot-3.png. If you plan to capture a refreshed UI screenshot, consider renaming the asset (e.g.,screenshot-engagement-boost.png) to make future maintenance clearer.
📜 Review details
Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (1)
README.md(5 hunks)
🧰 Additional context used
🪛 LanguageTool
README.md
[typographical] ~5-~5: Do not use a colon (:) before a series that is introduced by a preposition (‘to’). Remove the colon or add a noun or a noun phrase after the preposition.
Context: ...3.20.1 Requires at least: 6.0 Tested up to: 6.8 Requires PHP: 7.4 License: GPLv2 or...
(RP_COLON)
[uncategorized] ~130-~130: A comma may be missing after the conjunctive/linking adverb ‘Also’.
Context: ...gestions in the Post Editor's settings. Also available in the Parse.ly Editor Sideba...
(SENT_START_CONJUNCTIVE_LINKING_ADVERB_COMMA)
🪛 markdownlint-cli2 (0.17.2)
README.md
8-8: Bare URL used
null
(MD034, no-bare-urls)
⏰ Context from checks skipped due to timeout of 90000ms (2)
- GitHub Check: build
- GitHub Check: E2E against WordPress latest
🔇 Additional comments (1)
README.md (1)
42-42: Updated label points to an old-slug URL – double-check accuracyThe anchor text says “Engagement Boost”, but the link still targets
https://docs.wpvip.com/parse-ly/wp-parsely-features/traffic-boost/.
If the documentation URL will eventually adopt the new slug (engagement-boost), this link will 404. Otherwise, the mismatch could confuse readers.
maxschmeling
approved these changes
Jun 24, 2025
maxschmeling
left a comment
There was a problem hiding this comment.
Do we need to add redirects from the /traffic-boost URLs or are we ok without that?
Contributor
Author
@maxschmeling Good idea! This will help for any open tabs after the update is pushed, or if anyone has a bookmark set. Pushed 44dfb6e to fix that. Now Screen.Recording.2025-06-24.at.1.44.42.PM.mov |
github-actions bot
added a commit
that referenced
this pull request
Jun 24, 2025
…els-to-engagement-boost Change feature name "Traffic Boost" to "Engagement Boost"" (8e7df6f)
This was referenced Jun 24, 2025
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.
Description
Updates public-facing labels and URLs for "Traffic Boost" to "Engagement Boost":
For safety, this only updates visible labels and URLs but not internal references. We have 600+ instances of
traffic.*boostin our code, including object classes, function names, CSS classes, API endpoints, and internal settings options. These are more risky to update en masse, so I'm sticking to the admin-facing labels and URLs for this PR. A full internal rewrite to use "engagement boost" will take more effort and may require migration steps for strings like options keys.Motivation and context
"Traffic Boost" may imply some third-party traffic being sent to the site, so "Engagement Boost" may be more clear to customers.
Summary by CodeRabbit
Summary by CodeRabbit