You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* Rename the mdparivaar brand to Maanav
The community moves from mdparivaar.com to maanav.net. This renames the
brand throughout: directory, id, slug, scheme, display name, wordmark, and
the deep-link host.
Both hostname maps are updated together - src/brand/resolve.web.ts for the
client, which resolves from window.location.hostname, and the Go mirror in
bskyweb/cmd/bskyweb/brand.go, which drives SSR OG/Twitter metadata and the
pre-hydration splash colors. They have to agree or a visitor gets one
brand's link preview and another brand's page.
mdparivaar.com stays mapped to the maanav brand in both. The reverse proxy
301s it to maanav.net so the app should never see it, but if a redirect is
ever missed the entries keep the brand correct instead of silently falling
back to the default.
The Hindi welcome copy, composer prompt, saffron palette, and MD icon are
unchanged - the Madhyasth Darshan identity carries over. Only the Go
Description string, which surfaces in link-preview cards, is reworded.
The wordmark viewBox narrows from 126 to 80 to match the shorter word;
`ratio` drives the layout box, so leaving it at 126 would render "Maanav"
floating in dead space.
Native bundle ids remain TODO placeholders, renamed for consistency.
* Update brand resolution test fixtures for the Maanav rename
The port-stripping case used mdparivaar.com, which now resolves to the
maanav brand via the legacy fallback rather than to a mdparivaar brand that
no longer exists. Point it at the canonical maanav.net host, and add an
explicit case for the legacy mdparivaar.com -> maanav mapping since that
fallback is now load-bearing (the reverse proxy 301s it, but the entry keeps
the brand correct if a redirect is ever missed).
0 commit comments