mirror of
https://github.com/hanzoai/team.git
synced 2026-09-30 01:57:35 +00:00
zeekayandHanzo Dev
314e6b1b4f
The rebrand had reached the product's own words and stopped at its links, so
every screen that offers help still handed the reader to the other vendor:
the training menu opened their academy, Report a Problem composed mail to
their address and cited their Zendesk articles, Contact Support opened their
ticket form, and the OpenID, SAML, LDAP, theme and API-token pages linked
their documentation. Three emails we send asked people to write to their
support and feedback addresses, and the invitation footer — the most-read mail
in the product — linked their homepage.
Where the docs host was already ours the slug still was not, so a reader saw
docs.hanzo.team/upgrade-mattermost in the status bar. Those keep the host and
lose the name.
The admin console examples too: an S3 bucket called mattermost-media, an
allowed-domain list of corp.mattermost.com, a subpath of /company/mattermost.
Two constants named the other product and pointed at ours, which is the same
contradiction one level down; one had no readers at all and is gone.
WHAT STAYS, and why each is not branding:
*.push.mattermost.com the HPNS endpoints, a service that is theirs
translate.mattermost.com the Weblate these translations come from
mattermost ldap idmigrate, ./bin/mattermost, mattermost.log
the command, the binary and the file, by their names
MattermostAppID, {{.MattermostUsername}}
a JSON field on the API and a template variable
the copyright headers a licence notice
en.json is GENERATED, and the committed one had drifted from the sources in
three places: two keys edited there and not in the source — the app showed the
new string and the extractor put the old one back — and one pair the sort
comparator orders the other way. Regenerated, so the two agree again.
Co-authored-by: Hanzo Dev <[email protected]>