Refactor: rebrand user-visible strings from Liquid Web to Nexcess by glaubersilva · Pull Request #175 · stellarwp/harbor

glaubersilva · 2026-06-19T18:03:42Z

Summary

Rebrand Harbor user-visible branding
from Liquid Web to Nexcess (SMTNC-1494).

This is the strings-and-UX pass only. Portal URLs (software.liquidweb.com → software.nexcess.com) are intentionally deferred until backend redirect/go-live is confirmed with Product/Comms.

Branding & UI

Rename admin menu and page titles: Liquid Web Products → Nexcess Products, Liquid Web Software Manager → Nexcess Software Manager
Update React UI copy (welcome shell, filter bar, license sidebar, error messages)
Replace Liquid Web logo with Nexcess logo (nexcess-logo-light.svg) in the Software Manager header
Update legacy license page notices and partner submenu titles to Nexcess wording

Admin page slug (dual registration)

Canonical slug: nexcess-software-manager (Settings → Nexcess Products)
Legacy alias: lw-software-manager — permanently registered as a hidden page (no menu entry) so bookmarks and Leader mid-session transitions keep working when an older Harbor instance becomes Leader

Related PHP updates: asset enqueue, portal redirect refresh, and license notice suppression now accept both slugs.

Documentation & contributor workflow

Add CONTRIBUTING.md — primary local workflow via harbor-dev-tools (composer harbor:watch + npm run build/start)
Extract advanced partner-plugin path-repo setup into docs/guides/partner-plugin-testing.md
Update docs/guides/testing.md — harbor-dev-tools layout, fixture key guidance (lwsw-unified-basic-2026 for UI), canonical + legacy admin URLs
Update docs/guides/integration.md and README.md cross-links

Tests

E2E: Nexcess menu label, canonical slug, new legacy-slug smoke test
JS unit: WelcomeShell / AppLoader subtitle, activation-url redirect param, license error messages
PHP unit: dual slug registration, legacy hidden page, portal refresh on legacy slug, legacy notice copy

Built assets

Rebuilt build/ and build-dev/ frontend bundles to reflect logo and string changes

Out of scope (follow-up / separate branch)

Item	Notes
`Config::DEFAULT_PORTAL_BASE_URL`	Still `https://software.liquidweb.com`
Hardcoded support URL in `ErrorModal.tsx`	Still points at `software.liquidweb.com/support/`
Technical identifiers	Namespaces, hooks (`lw_harbor/`), REST namespace, `LWSW-` license prefix, DOM/CSS `lw-harbor-` — unchanged

Do not merge until coordinated with customer comms (Emily Negroni).

Test plan

Local setup with harbor-dev-tools + Harbor clone at wp-content/plugins/harbor
Run composer harbor:watch (harbor-dev-tools) and npm run build (harbor)
Welcome gate (no license): subtitle shows Nexcess; Nexcess logo visible
Software Manager at ?page=nexcess-software-manager: menu Settings → Nexcess Products, Nexcess logo in filter bar, “Manage license in Nexcess” link label
Legacy slug ?page=lw-software-manager: page loads with same UI (no Settings menu entry for legacy slug)
Legacy license notice (lw_harbor_display_legacy_license_page_notice) shows Nexcess copy
Automated tests: npm run test:unit, PHP unit suite, E2E specs
Confirm portal/subscription links still resolve to software.liquidweb.com (expected until URL follow-up)

Screenshots

Linear

https://linear.app/nexcess/issue/SMTNC-1494/update-plugin-branding-from-liquid-web-to-nexcess

…TNC-1494) Update all user-facing text, page slugs, and menu labels to Nexcess branding. PHP - Feature_Manager_Page: change PAGE_SLUG to 'nexcess-software-manager' and permanently register 'lw-software-manager' as a hidden alias so bookmarks and Leader mid-session transitions remain functional after the rebrand. Add $page_hook_legacy so assets are enqueued on both slugs (fixes blank page when visiting the legacy URL). - Feature_Manager_Page: update page title to "Nexcess Software Manager" and Settings menu label to "Nexcess Products". - Display_Legacy_License_Page_Notice: update notice body text to "Nexcess's software offerings" / "Nexcess Software Manager". - global-functions.php: update docblock for lw_harbor_display_legacy_license_page_notice(). React - FilterBar: update logo alt text and heading. - WelcomeShell: update brand subtitle. - LicenseSection: update portal link label to "Manage license in Nexcess". - harbor-data-context, use-resolvable-select-with-error: update fallback error messages. - store/actions, store/resolvers: update all error strings to "Nexcess Software Manager failed to…". Docs - Add CONTRIBUTING.md: prerequisites, scripts reference, and a step-by-step local-testing workflow for validating Harbor changes against a partner plugin via Composer path repository without publishing a release. - Link CONTRIBUTING.md from README.md.

linear · 2026-06-19T18:03:46Z

SMTNC-1494

…nto refctor/SMTNC-1494-rebranding

Center local development on harbor-dev-tools instead of duplicating its README, and move the advanced Composer path-repo workflow out of CONTRIBUTING into docs/guides/partner-plugin-testing.md.

Align JS, PHP, and E2E tests with the new admin page slug, menu label, user-facing copy, and activation redirect URL after the Liquid Web → Nexcess rebrand.

Rebuild frontend assets after resolving build/ conflicts from main. Co-authored-by: Cursor <cursoragent@cursor.com>

Use empty parent slug for hidden legacy admin page (PHPStan), align CONTRIBUTING prerequisites table, and add doc tooling terms to cspell.

Center day-to-day setup on harbor-dev-tools (PHP and UI), clarify the plugins directory layout, and drop duplicated sections in favor of the documentation index.

Replace the outdated sample-plugin fixture guide with harbor-dev-tools setup, update integration guide Nexcess copy, rebrand the partner submenu label, and add PHP/E2E tests for the lw-software-manager alias.

d4mation · 2026-06-30T17:21:27Z

+(see [CONTRIBUTING.md](../../CONTRIBUTING.md) or the [harbor-dev-tools README](https://github.com/stellarwp/harbor-dev-tools/blob/main/README.md)). Use the path repository workflow below only
+when you must test **local changes** inside a real partner plugin.


Maybe we should include an example case of when you'd need to test them inside a real partner plugin. Because I've yet to come across the need for this personally 😅 The way the "Leader" system works using Harbor Dev Tools has always been enough for me. But I think maybe @jonwaldstein has had a need to do something similar to this.

The reason I created it is that I spent some time doing this setup before discovering harbor-dev-tools, so I kept this guide just in case other developers need to do something similar in the future for some reason. Since I alredy spent some Claude Code tokens on it, others do not need to spend more if we keep it here.

Hey guys, most of the time harbor-dev-tools does the job but there have been cases where I needed to bundle harbor in our real plugins locally to test specific scenarios like the last leader notice that happens in the UI because of their relationship with other add-ons. It's really tedius when Strauss is involved and is not recommended unless you have to lol 😄

d4mation · 2026-06-30T17:24:52Z

+### Docker / Lando
+
+The Composer command runs inside a container that only mounts the partner plugin's site
+directory. The Harbor checkout is not visible inside the container by default.


This seems hyper-specific to a certain workflow. When would you need to do this in favor of a less complex solution? Is this specific to a certain brand's suggested local environment configuration?

Yes, this Docker / Lando section is specific to those who are using Lando to work on a specific brand, and it can be basically any brand if you are using Lando to create local sites for all of them, like I'm doing these days.

Yeah, but when would you need to run these commands, specifically? I use Lando and haven't needed to do this. I mount Harbor Dev Tools+the Partner Plugin I'm working on as volumes and then Harbor just exists on my machine.

When running Harbor Dev Tools' Watch command (or any other composer command) on my machine, it would naturally just sync into the Lando container via its volume mount.

It looks like you're wanting to run everything within Lando's container (which is definitely good to ensure that we're all using identical tooling/versions/etc.) but then maybe we should ship Harbor with a dedicated Lando environment for that instead. Then when testing with a Partner Plugin, it becomes a wholly Harbor concern with Harbor's local environment. Then when developing for things that are not Harbor-related, a developer could choose whatever environment they would like.

Ok, now I get it. The doc was confusing on that point.

These steps are only necessary when testing with Harbor outside the site root, like the path I was using when setting this up: ~/Dev/libs/harbor.

I've updated the doc to make that clearer: df3682c

Thanks for questioning that, and let me know if there is something else.

d4mation

One small thing, but then I think we should be good to merge this :)

Thanks for the improved docs!

d4mation · 2026-07-06T20:04:11Z

+	/**
+	 * Legacy admin page slug kept permanently registered so bookmarks and
+	 * Leader mid-session transitions remain functional after the rebrand.
+	 *
+	 * @since TBD
+	 */
+	public const PAGE_SLUG_LEGACY = 'lw-software-manager';


Do we need this to be public? Is there a case when any third party code would reasonably want to reference the legacy page slug manually?

We only have this fallback for edge cases when options-general.php?page=lw-software-manager may have been hardcoded somewhere instead of lw_harbor_get_license_page_url() or lw_harbor_register_submenu() being used as-expected.

Feature_Manager_Page::PAGE_SLUG is used by lw_harbor_get_license_page_url() directly so any callers will automatically see this change, and lw_harbor_register_submenu() uses it in the background when registering itself as a submenu for something like Kadence, Give, etc.

harbor/src/Harbor/API/Functions/Global_Function_Registry.php

Lines 126 to 132 in 567d537

\_lw_harbor_global_function_registry(

'lw_harbor_get_license_page_url',

$version,

static function (): string {

return admin_url( 'options-general.php?page=' . Feature_Manager_Page::PAGE_SLUG );

}

);

Yeah, it makes sense! Resolved in 6658689

Also in 725511a and 85bf45c

Add `is_known_page_slug()` static helper to Feature_Manager_Page that tests both canonical and legacy slugs in one place. Update License_Notice_Handler to call the new method instead of duplicating the slug comparison logic.

… tests

glaubersilva · 2026-07-07T23:24:44Z

@d4mation Thanks for the comments. This is ready for a new review!

glaubersilva and others added 2 commits June 19, 2026 15:02

Build frontend assets

f07cbfe

glaubersilva self-assigned this Jun 19, 2026

glaubersilva changed the title ~~refactor: rebrand user-visible strings from Liquid Web to Nexcess (…~~ refactor: rebrand user-visible strings from Liquid Web to Nexcess Jun 19, 2026

glaubersilva changed the title ~~refactor: rebrand user-visible strings from Liquid Web to Nexcess~~ Refactor: rebrand user-visible strings from Liquid Web to Nexcess Jun 19, 2026

glaubersilva and others added 12 commits June 19, 2026 15:36

refactor: replace LW logo with NX logo

d980917

Merge remote-tracking branch 'origin/refctor/SMTNC-1494-rebranding' i…

ab319e2

…nto refctor/SMTNC-1494-rebranding

Build frontend assets

a771c9f

docs: streamline CONTRIBUTING and extract partner-plugin testing guide

ebc0414

Center local development on harbor-dev-tools instead of duplicating its README, and move the advanced Composer path-repo workflow out of CONTRIBUTING into docs/guides/partner-plugin-testing.md.

tests: update expectations for Nexcess rebrand (SMTNC-1494)

92ed23a

Align JS, PHP, and E2E tests with the new admin page slug, menu label, user-facing copy, and activation redirect URL after the Liquid Web → Nexcess rebrand.

Merge branch 'main' into refctor/SMTNC-1494-rebranding

9ba2218

Rebuild frontend assets after resolving build/ conflicts from main. Co-authored-by: Cursor <cursoragent@cursor.com>

fix: resolve CI lint failures after main merge

974f262

Use empty parent slug for hidden legacy admin page (PHPStan), align CONTRIBUTING prerequisites table, and add doc tooling terms to cspell.

docs: streamline CONTRIBUTING quick start for harbor-dev-tools workflow

8f3ddab

Center day-to-day setup on harbor-dev-tools (PHP and UI), clarify the plugins directory layout, and drop duplicated sections in favor of the documentation index.

fix: satisfy cspell in CONTRIBUTING.md

bff93e9

refactor: document harbor-dev-tools workflow and legacy slug coverage

977018a

Replace the outdated sample-plugin fixture guide with harbor-dev-tools setup, update integration guide Nexcess copy, rebrand the partner submenu label, and add PHP/E2E tests for the lw-software-manager alias.

doc: add since TBD tags

3315b20

Build frontend assets

19dec0b

glaubersilva marked this pull request as ready for review June 30, 2026 17:12

glaubersilva requested review from d4mation, jonwaldstein and pauloiankoski June 30, 2026 17:12

d4mation reviewed Jun 30, 2026

View reviewed changes

glaubersilva added 2 commits June 30, 2026 19:54

docs: clarify partner-plugin-testing environment paths and scope

df3682c

chore: add docroot to cspell.json exclusion

f526678

d4mation reviewed Jul 6, 2026

View reviewed changes

glaubersilva added 3 commits July 7, 2026 20:11

refactor(admin): restrict PAGE_SLUG_LEGACY visibility to private

6658689

test(admin): replace PAGE_SLUG_LEGACY constant with literal string in…

85bf45c

… tests

glaubersilva requested a review from d4mation July 7, 2026 23:24

d4mation approved these changes Jul 8, 2026

View reviewed changes

		(see [CONTRIBUTING.md](../../CONTRIBUTING.md) or the [harbor-dev-tools README](https://github.com/stellarwp/harbor-dev-tools/blob/main/README.md)). Use the path repository workflow below only
		when you must test local changes inside a real partner plugin.

	\_lw_harbor_global_function_registry(
	'lw_harbor_get_license_page_url',
	$version,
	static function (): string {
	return admin_url( 'options-general.php?page=' . Feature_Manager_Page::PAGE_SLUG );
	}
	);

Uh oh!

Conversation

glaubersilva commented Jun 19, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Summary

Branding & UI

Admin page slug (dual registration)

Documentation & contributor workflow

Tests

Built assets

Out of scope (follow-up / separate branch)

Test plan

Screenshots

Linear

Uh oh!

linear Bot commented Jun 19, 2026

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

d4mation Jun 30, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

d4mation left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

glaubersilva commented Jul 7, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

glaubersilva commented Jun 19, 2026 •

edited

Loading

d4mation Jun 30, 2026 •

edited

Loading