Rebrand Experience plugin UI for Fueled 1.19.0

[jakemgold]

Summary

• Rebrands the plugin's customer-facing metadata, WordPress admin-bar menu, footer attribution, welcome notice, plugin-row details action, and recommended-plugin messaging for Fueled.
• Replaces the legacy About 10up screen with a redesigned About Fueled page.
• Adds a dedicated Experience Plugin page showing current site configuration, built-in safeguards, Support Monitor disclosures, and links to settings and technical documentation.
• Adds Fueled visual assets and rebuilt distribution files.
• Prepares version 1.19.0 with proposed release notes.

Why

The plugin still presented substantial 10up branding and an outdated agency introduction inside client WordPress installations. This update brings customer-visible surfaces in line with Fueled while explaining the plugin's purpose and behavior more clearly.

Compatibility

This deliberately preserves the existing plugin folder and main filename, PHP namespace, constants, settings and user-meta keys, hooks and filters, text domain, page slugs, updater configuration, SSO plumbing, and Support Monitor endpoint. No migration is expected.

Known follow-up

The Fueled Recommended tab is still populated from the WordPress.org favorites associated with the 10up account. #234 tracks intentional curation, ownership, and future handling of that list. This PR changes its customer-facing label and explanatory copy but does not change its source.

Validation

• Reviewed and tested the redesigned pages and related WordPress admin surfaces in the local pluginsites.local LocalWP environment.
• npm run build
• npm run lint-style
• npm run lint-js
• composer lint with zero errors; seven pre-existing warnings remain in untouched files.
• PHP syntax checks across project PHP files.
• git diff --check

Review status

This is intentionally a draft for initial visual, content, and implementation review. Please do not merge until the Fueled branding direction and release scope are coordinated.

Relates to #187.
Follow-up: #234.

[darylldoyle]

The REST API option can also be set at the code-level but this only reads from the DB. We should consider extracting the logic in https://github.com/10up/10up-experience/blob/develop/includes/classes/API/API.php#L91-L95 into a reusable helper within the API class. Something like:

/**
 * Whether REST API restriction is actually enforced.
 *
 * Returns false when either restriction filter has been unhooked at the code
 * level, in which case the stored option no longer describes real behaviour.
 *
 * @since 1.19
 * @return bool
 */
public function restrictions_are_enforced() {
    return has_filter( 'rest_authentication_errors', [ $this, 'restrict_rest_api' ] )
        && has_filter( 'rest_endpoints', [ $this, 'restrict_user_endpoints' ] );
}

This could then be added to the check.

I don't think this is critical, just wanted to call it out.

[claytoncollie]

@jakemgold This looks very sharp :)

I ran an automated review against the code and also pulled it down locally to verify.

Below are some suggestions that we might want to consider.

1. Consistent external link targets. Off site links open in a new tab on the About and Experience pages and the admin bar dropdown, but in the same tab from the footer and the Plugins screen. Should we pick one method?

2. Higher contrast status pills. The .experience-status__value states (.is-active, .is-informational, .is-muted) are hard to distinguish. Suggest raising contrast of background color.

3. "Monitor," not "Support Monitor." Update both the label and description of the Support Monitor item in get_experience_configuration(); check other occurrences too.

4. Spell out SSO. Change the "Fueled SSO" card label to e.g. "Fueled Single Sign On (SSO)."

5. REST API pill wraps on laptops. "User endpoints protected" wraps below full desktop width. Suggest shortening it or keep the pill on one line with CSS.

6. Reconsider "We make WordPress." on the About page near the bottom. Given the WP Engine litigation and WordPress trademark sensitivity. Suggest contribution framing, e.g. "We help build WordPress."

[jeffpaul]

@darylldoyle we'll likely want to consider this alongside #236 as both do some rebranding across the plugin and will want to ensure they work well together / don't conflict, else will need to pick on to continue with and the other to close out.

[jeffpaul]

May also want to consider doing the 10up > Fueled work as part of a 2.0.0 version to mark the change more formally?