Rebrand the template

Rebranding the remix template is token and copy work, not component rebuilding: you change design variables, swap a handful of assets, rewrite text, and update legal and SEO metadata so the site is unmistakably yours. Because the template is built on a shared token system, most visual changes propagate automatically once you update the tokens, leaving component code untouched.

Design tokens

The shell stylesheet defines colour, spacing and radius as variables rather than hard-coding them into components. Change the primary, secondary and accent colours, the border radius scale, and any semantic tokens (success, warning, error) there, and every page, button and form field that references them updates consistently. Avoid overriding colours inside individual components — it works in the short term but drifts out of sync the next time you adjust the palette.

Logo and favicon

Replace the logo asset used in the header and footer, and update its alt text to your product name for accessibility and SEO. Separately replace the favicon and any app icons used for browser tabs, bookmarks and social share previews — these are easy to forget because they live outside the main component tree, in the public assets folder and the document head.

Typography

Update the display and body font variables to your brand's typeface pair. Check headings, body copy, buttons and form inputs all inherit the new fonts correctly, since some components may set font-family explicitly rather than inheriting from the root variable — those are the exceptions worth searching for and fixing.

Copy

Rewrite marketing page copy, onboarding and empty-state text, and any placeholder product name references throughout the console. This is largely a search-and-replace exercise for the template's placeholder brand name, but it is worth reading each page rather than relying purely on find-and-replace, since some copy references Arino-specific concepts (like the Arino Core connection) that may not apply to how you present your own product.

Legal pages and entity details

The legal entity operating the product in front of your customers is you, not Arino, regardless of whether you self-built the template or had Arino build it, and regardless of whether you take the optional $50/month Arino Core connection. Update the privacy policy, terms of service and cookie policy with your own legal entity name, registered address and DPO contact, and remove any residual references to Arino in these pages. This matters for consent and data-protection obligations — your customers are consenting to your processing of their data, not Arino's.

Domain and SEO metadata

Point your production domain at the deployment, then update page titles, meta descriptions, canonical URLs and the Open Graph image used for social previews. Regenerate the sitemap and check the robots configuration so it references your domain rather than the template's placeholder one. Left unchanged, these details either point search engines and social previews at the wrong domain or expose the fact that the site began life as a template.

What must not be changed

Two things should stay as they are: the content model and docs index structure, and the front end's API integration with the back-end instance. The content model is what keeps documentation organised and searchable as your product grows, and restructuring it breaks that organisation without adding value. The API integration is what lets the front end talk to your instance, connected to your own Infobip account — rebranding never needs to touch it, and doing so risks breaking the connection covered separately in connecting the template to your instance.

A practical sequencing

Most teams tackle these in the order above — tokens first, then assets, then copy, then legal and metadata last — because tokens and assets have the broadest visual impact and are quick to verify, while legal and SEO details are easy to check off in a final pass before launch. Doing legal and metadata last also avoids repeating that work if copy changes shift entity references partway through.

Steps at a glance

1. Replace design tokensUpdate colour, spacing and radius tokens in the shell stylesheet rather than editing individual components, so the change propagates across the whole site.
2. Replace the logo and faviconSwap the logo asset, update its alt text, and replace the favicon and app icons used in the browser tab and share previews.
3. Set the typography pairUpdate the display and body font variables to your brand's typeface, checking that headings, body text and form fields all inherit correctly.
4. Rewrite marketing and product copyReplace placeholder copy on marketing pages, empty states and onboarding screens with your own product name and messaging.
5. Update legal pages and entity detailsReplace the legal entity name, registered address, DPO contact and any references to Arino in privacy policy, terms and cookie pages with your own.
6. Update domain and SEO metadataPoint the custom domain at your deployment and update page titles, meta descriptions, Open Graph images and the sitemap to reflect your brand.

Frequently asked