​

How to use the press kit

The press and brand resources page gives you the assets; this guide is the usage manual for the team that picks them up — which variant goes where, which naming rule is non-negotiable, how localization works, and how to keep quoted boilerplate from going stale. It mirrors the companion blog post (A PR team’s guide to the Devotel Orbit press kit), which is the editorial anchor for trade-press outreach.

​

The asset taxonomy

Everything the kit ships falls into four asset classes and one routing contact: Pull from the live press kit page, not from a screenshot of the site or a stale deck.

​

Naming and logo guardrails

Two rules are non-negotiable, and the first is the one most drafts violate:

1. The full product name is “Devotel Orbit.” Bare “Orbit” is acceptable only in running text after the full name is established once — headlines, deck titles, and link anchors always use the full name.
2. “Orbit.com” is never written. The product lives at orbit.devotel.io; the company at devotel.io. Any other orbit-* domain is invented and wrong.

The remaining logo rules:

• Keep the aspect ratio as delivered — never stretch, redraw, or recolor the mark.
• Use the colored logo on light surfaces and the white logo on dark ones; fall back to the mono logomark when only one ink is available.

​

Localization across six locales

The kit renders in the six locales the product ships — English, Turkish, Arabic, German, French, and Spanish — under a locale-prefixed URL (/en/press-kit, /tr/press-kit, and so on).

1. Pull boilerplate and facts from the locale your piece targets; the SVG assets themselves are locale-independent.
2. The naming rules do not localize — “Devotel Orbit” is written the same in every locale, including Arabic-script copy.
3. Press-desk routing does not localize — press@devotel.io answers in the language the inquiry arrives in.

​

Chain-of-custody: keep press quotes in step with releases

The failure mode a PR team actually hits is a stale boilerplate, not a wrong logo. The fix is a loop:

1. Watch the changelog and the announcements hub. Any entry that touches positioning, naming, coverage, or company facts is a candidate press-kit refresh trigger.
2. Re-pull on positioning releases. When a release changes what the product is, the boilerplate and facts panel are re-cut in the same cycle — re-pull rather than carrying forward last cycle’s copy.
3. Version the pull, not the kit. Every asset lives at a stable public URL, so for a PR team “sync” means: record the pull date in the outreach doc, re-pull on positioning releases, and re-quote verbatim.
4. Corrections go through the press desk. If a circulating quote is wrong, the desk issues the corrected length and a correction note — a PR team does not silently update its own copy.

​

Where this fits

• Assets: press kit (product site) or press and brand resources (this docs page).
• Editorial anchor: the press-kit usage blog post.
• Company background: /about.
• Anything not on the kit: /contact or press@devotel.io.