Rebrands

A rebrand consists of brand style guide changes – fonts, colors, etc. These updates will need changes to the Vibram environment for a school or program. A kickoff meeting is the first step to get this going! 

Web Strategy & Operations turnaround times for Rebrands are handled on a program-by-program basis. Please plan to discuss at the kickoff meeting.

Degree Rebrand Charter – Degree Rebrand Charter maintained by Marketing Operations
Sitemap Template

Things to Remember

  • Sitemap must include PLPs and TYPs
  • Audits of images/assets should be addressed during the kickoff meeting, as the creative team will need time to gather assets. Align on who owns this upfront.
  • Any changes to fonts need to be handled carefully. When the font file is deleted within Vibram, it impacts the LIVE site.

Steps within the Rebrand Process

Each rebrand process will differ, but this is generalized list of necessary steps:

  1. Marketing Tech will need to clone the environment – ticket needed
    • Once Marketing Tech clones the environment, the live site should enter a freeze period so that we’re not updating content on the live site and forgetting to do it on the staged site. Please reach out to the Web Production Manager for any urgent tickets that need to be addressed during the freeze.
  2. Marketing Ops/Web Prod to inform Marketing Tech of goal go-live day.
  3. Marketing Ops to connect with SEO to obtain a sitemap. Sitemap should include links for the entire site, especially the hidden pages, PLPs and TYPs. – ticket needed
  4. Marketing Ops to create tickets for Creative to update staged Vibram (new icons, new colors, new fonts, etc.) – ticket needed
  5. Marketing Ops to create tickets for Creative to provide updated assets (icons for example) – ticket needed
  6. Web Prod syncs Vibram UUID with the staged WordPress environment.
  7. Web Prod to start the process of staging the newly designed pages. This should include PLPs and TYPs. – ticket needed
  8. Web Prod to involve Marketing Operations & Creative in the QA process for the staged environment and note any changes needed.
  9. Web Prod to implement any edits from QA.
  10. Send to school for review – can be optional or required (Marketing Ops to answer)
  11. Web Prod to implement any school feedback.
  12. Marketing Ops/Web Prod to update Marketing Tech on goal go-live day if there are any changes to original plan.
  13. Marketing Tech to coordinate launch with Big Bite.
  14. On launch date, Creative to update & push live the Prod Vibram. – ticket needed
  15. On launch date, Web Prod to switch UUID in Vibram settings to be original UUID, not the staged UUID. – ticket needed