Official:Rebranding Guidelines: Difference between revisions

From Official Kodi Wiki
Jump to navigation Jump to search
No edit summary
No edit summary
Line 28: Line 28:




For a full rebrand to allow the new product to run side by side with and entirely independently of the XBMC Foundation product, the data in the [https://github.com/xbmc/xbmc/blob/29cbd865f65d5d866427c29119afe7725c79daad/version.txt version.txt] file should also be modified to reflect the new product identity. Note that this may require forking of the binary addon set as well to ensure compatibility.
For a full rebrand to allow the new product to run side by side with and entirely independently of the XBMC Foundation product, the data in the [https://github.com/xbmc/xbmc/blob/29cbd865f65d5d866427c29119afe7725c79daad/version.txt version.txt] file should also be modified to reflect the new product identity. There are some notes on this however:
 
:* Modifying the APP_NAME will also change the folder in which the product stores its user data and installed addons.
:* This may require forking and modification of the binary addon set as well to ensure correct operation.





Revision as of 19:40, 28 January 2020

Home icon grey.png   ▶ XBMC Foundation ▶ Trademarks ▶ Rebranding Guidelines


Referenced Pages and Further Reading


Guidelines

The rule of thumb for rebranding is to remove any XBMC Foundation trademark, wordmark or logo that is user-facing and visible during normal operations of the product.


A non-exhaustive list of suggested items are:

  • The default skin used by the product.
  • Remove the main splash screen or replace them with suitably rebranded ones.
  • The name of the default update repository (although sync'ing with the XBMC Foundation official repo is acceptable).
  • Logos in Estuary or any other official skin if pre-installed.
  • The new brand should have its own distinct privacy policy.
  • Logos and marks (including favicons) for any pre-installed web interface(s).
  • The default system names used for identification to networked services such as AirPlay and Bonjour.


For a full rebrand to allow the new product to run side by side with and entirely independently of the XBMC Foundation product, the data in the version.txt file should also be modified to reflect the new product identity. There are some notes on this however:

  • Modifying the APP_NAME will also change the folder in which the product stores its user data and installed addons.
  • This may require forking and modification of the binary addon set as well to ensure correct operation.


All translations should also be included in these changes.


Building Rebranded Versions

To assist in the building of the rebranded versions, any 3rd party artwork placed into the special://xbmc/media/ folder will be used in place of the default XBMC Foundation logos.


Similarly the graphics in the following folders should be updated with vendor artwork, depending on which platform(s) are being built: