Turleno brand guide

Tek cümle (TR)

Turleno: iş seyahatinizi yapay zekâ halleder. Nereye, ne zaman gitmeniz gerektiğini söyleyin, gerisini Turleno yapsın: şirket politikanıza uygun uçuş, otel ve araç hazır, onay alınmış, bilet cebinizde. Seyahat acenteniz de her adımda yanınızda.

One-liner (EN)

Turleno: business travel, handled by AI. Say where you need to be and when; Turleno does the rest: flights, hotel and car inside your company's policy, approval taken, ticket in your pocket. Your travel agency stays with you at every step.

Çalışan · Employee

Söyleyin, gerisini Turleno yapsın.

Tell it where you need to be. It's handled.

Acente · Agency

Aynı ekiple daha çok müşteri.

More clients, same team. Turleno's AI does the bookings; the agency keeps price negotiation and the personal relationship. Its logo and name on the app, its margin, its client.

Finans ve yönetici · Finance and manager

Her seyahat, var olmadan önce politika, bütçe ve onaydan geçer.

Every trip fits policy, budget and approval before it exists.

Now

Text Turleno on web chat or WhatsApp. Get policy-checked options. One-tap approval. Booked. Agency notified, balance updated.

Next (roadmap, always labelled as such)

Turleno reads the trigger (a calendar invite, an email, the company's own AI) and proposes the full trip before anyone asks.

Tagline, category label and naming

What we may claim

• Web chat and WhatsApp assistant
• Flights via THY, Pegasus, AJet (NDC) and Travelport
• Hotels via an integrated supplier plus agency offline inventory with approval
• Car rental (Enterprise Türkiye); transfer and visa requests priced by the agency
• Destination-scoped policy rules with soft and hard severity
• Prepaid, credit and hybrid company models; TRY ledger
• Magic-link login; Postgres row-level tenant isolation
• Core application infrastructure hosted in the EU (Frankfurt); e-tickets and vouchers; TR/EN interface

What we never claim

• A mobile or native app
• SSO, Google or Microsoft login
• Multi-currency billing or percentage markups
• Multi-step approval chains
• Tamper-proof audit or complete GDPR erasure
• Agency-coloured or white-label themes: every agency sees the Turleno design language, and an agency supplies only its logo and name
• Slack, other suppliers, a platform-owner console
• "Powered by Claude" or "Powered by ChatGPT". The assistant is Turleno.

The "coming" list is allowed and short: mobile app, SSO, expense-system sync, proactive trip planning. Never use the words "coming soon" on the site.

Primary wordmark, read closely

Gece Lacivert letters, Varış Mavisi "o". This is the default everywhere.

What the shape says

"Wordmark küçük harflidir. "t" harfinin yatay çubuğu sola taşar: kalkış. "o" vurgu renginde ve hafif yukarıda durur: varış noktası, konum işareti. Wordmark tek başına ana logodur. Ayrı ikon gerektirmez."

Source: Marka Kimliği v1.0, page 2.

Primary · ana logo

Navy letters, Varış Mavisi "o", on Krem, Beyaz or any flat light ground.

Reverse · koyu zeminde beyaz

White letters, Varış Mavisi "o", on Gece Lacivert or Derin Mavi.

One colour, navy · tek renk

Navy on Varış Mavisi, as in the PDF. The same file works on white and in one-spot print.

One colour, white · tek renk

For dark grounds we do not control: an agency's charcoal footer, a trade-fair wall, a video end card.

Which colourway, where

The wordmark stands alone

The wordmark is the main logo and needs no icon beside it. The ring icon (section 3) is a separate mark for small square slots. The two are never combined into a lockup, and never set side by side.

The tagline and the category label may sit near the wordmark in a layout, but they are not part of the logo and are never locked under it.

About the master files

The PDF ships the wordmark only as a raster image, so the vector master in the kit was rebuilt from it (it matches the PDF raster at an IoU of 0.995). Use the kit files, never a retyped "turleno".

A designer-drawn vector should replace the master before any large-format print (follow-up BRAND-FU-WORDMARK-VECTOR).

"Powered by Turleno" lockup

Clear space

"Wordmark'ın etrafında en az "o" harfinin yüksekliği kadar boşluk bırak." The unit is the height of the "o", about 15 % of the wordmark's width (60 px on a 400 px wordmark). Keep at least one unit of empty space on every side. Nothing enters this zone: no text, no partner logo, no rule, no edge of the page. For the "Powered by Turleno" lockup the unit is taken from its own "o" and the zone is drawn around the whole lockup.

Minimum size

The icon minimum of 16 px is from the PDF. The wordmark minimums and the print icon size are our own guidance, not from the PDF. Where a slot is smaller than the wordmark minimum, use the app icon alone. Never squeeze the wordmark.

Placement beside a partner logo

Right and wrong · doğru / yanlış

Usage rules · kullanım kuralları

Four variants · dört versiyon

Proportions

The numbers

"Minimum: 16 px. Halka kalınlığı ikon genişliğinin ~%10'u, merkez nokta çapı ~%20'si. Bu oranlar korunur."

Keep these proportions. Never redraw the ring: export it from the kit.

Small-size test · küçük boyut

The ring and its open centre stay distinct down to 16 px, which is the minimum. Below that, do not use the icon.

Rules

• Never beside the wordmark. The icon and the wordmark are two separate marks. Do not lock them up, do not set them next to each other.
• The icon keeps its own ground. It is not placed on a busy image and not recoloured; the ring is white on a tile, or Varış Mavisi on the Açık tile.
• No gradient, shadow, glow or 3D on the icon. Platforms that add their own corner mask get the maskable file.
• Agencies may not use it as their own app icon, avatar or favicon (section 4).

The cover of this guide follows the PDF's cover: the wordmark at the top, the icon alone in the far corner.

Uses

What an agency supplies

"Her acente aynı Turleno tasarım dilini görür; acente yalnızca logosunu ve adını getirir."

• A logo and a name, nothing else. They sit in the logo slot at the top left of the app shell, shown as supplied on a white ground, at most 32 px tall. The name sits beside the logo in 14 px Inter Medium.
• Agency colours never enter the UI. No agency-coloured buttons, navigation, links, charts or loading screens. The logo slot is the only place an agency's colours appear.
• Turleno signs at the foot. "Powered by Turleno" sits at the foot of the sidebar, on the app-loading screen and in the chat footer.

One look for every agency also means one set of statuses, one set of buttons and one set of screenshots for support and sales.

In the app shell

The agency's colours appear only in the logo slot (top left). Everything else is Turleno's: cool grey canvas, white cards, one status pill, the lockup at the sidebar foot.

The product lockup

In the app the lockup is built live: the label "Powered by" in 13 px Inter Medium in muted-foreground (#4A5A73), an 8 px gap, then the wordmark on a shared baseline. In the product the wordmark is rendered 16 px tall, which makes it 73 px wide and keeps it over the 72 px wordmark minimum; the whole lockup is about 150 px wide, the lockup minimum. The label is always English, never translated.

The pre-built kit files (section 12) are outlined art with a Poppins Medium label. Use them in documents, emails, vouchers and video; build the live lockup only inside the app.

Which brand leads

In the app, the agency's logo and name lead the shell, and the Turleno design language fills the rest. Turleno appears as the "Powered by Turleno" credit at the foot.

In documents the agency sends (notification emails, vouchers, itineraries, WhatsApp) the agency's own brand leads and Turleno appears only in the footer credit.

Turleno leads only in Turleno's own sales material: the website, decks, case studies, trade-fair stands. There the agency appears as a partner, written as "Gezi Tur ile birlikte", after the Turleno mark and never merged with it.

Sizing in documents and emails

Beside an agency logo, the pre-built "Powered by Turleno" lockup is at most 60 % of the agency logo's height, and never below the lockup minimum (150 px wide on screen). If the agency logo is so small that 60 % would fall below the minimum, scale the agency logo up. Never scale Turleno below its minimum to make it fit.

The 60 % rule replaces any matching of x-heights or cap heights. Measure the agency logo's full height and the Turleno lockup's full height, nothing else. Inside the app the logo slot (at most 32 px) and the 16 px wordmark are fixed, so no ratio is needed.

Colour clashes

• Inside the app there is none to solve. The logo slot is white, and the Turleno interface around it never takes the agency's colours.
• Full colour (navy letters, Varış Mavisi "o") on Krem, Beyaz or navy grounds; the reverse lockup on dark grounds.
• One-colour lockup (navy or white) when the agency's document ground is any other colour, or when the agency's primary colour is a blue close to Varış Mavisi.
• Never recolour the mark into the agency's colours, not even to "match the footer".

Do and don't · documents and emails

Where the credit may appear

What agencies may not do

• Alter, animate, translate or crop the mark or the lockup.
• Theme the app with their own colours, or ask for agency-coloured buttons, navigation, links or charts.
• Use the Turleno ring icon as their own app icon, avatar or favicon.
• Put "Turleno" in a product name, domain, social handle or ad keyword.
• Suggest that Turleno sells the trip, sets the price or is the travel agency. In Türkiye only a TÜRSAB-licensed agency may sell travel; Turleno is software, not a licensed agency, so wording that makes it look like the seller misleads the traveller and puts the agency's own licence at risk.
• Keep using the mark more than 30 days after the contract ends.

Requests and files

Agencies receive the lockups pre-built, in both colourways, in the agency co-brand pack (section 12), and supply their logo and name for the app's logo slot. They never build their own lockup. Any placement not listed above goes to brand@turleno.com before it is produced. We reply within 5 working days.

Core palette · renk

Print values: TBD. CMYK and Pantone references are not set yet. They will be confirmed from a printed drawdown on the real stock; approve from a printed sample, never from a screen. The hex and RGB values above are the PDF's.

Navy brand region

Where: the one navy region of a view: the login's brand panel, the marketing site's agency panel, the cover of this guide. It sits on the cool canvas like everything else. Ground: Gece Lacivert, white text. Accent: Varış Mavisi. Button: Varış Mavisi fill with a navy label.

Product surface

Where: everything inside the app. Ground: background #F7F8FA, card #FFFFFF, muted #EEF1F5, all cool and navy-tinted. Action: #2A5BC8 with a white label. Never mix warm and cool neutrals on one screen.

Which blue, where

Varış Mavisi is a colour for dark grounds. On white or Krem it falls to 2.8 to 3.2:1, which fails for text and is borderline for graphics, so on light grounds it appears only in the logo "o" and the app icon. Inside the one navy region it is the accent and the button. Never use the action blue on navy (2.7:1).

Usage ratio · oran

Brand pieces: print, social cards, email

Every web page (app, login, site, legal, guide)

"Oran: marka yüzeylerinde ~%60 krem/beyaz, ~%30 lacivert, ~%10 mavi; üründe ~%85 zemin, ~%10 metin, en çok %5 mavi." On brand pieces (print, social cards, email) roughly 60 % cream and white, 30 % navy (Derin Mavi counts with it), 10 % Varış Mavisi. On every web page, the product included, about 85 % grounds (background and card), 10 % text and lines, and at most 5 % blue. If the blue covers much more than that, the screen has stopped being calm.

• One primary button per view; everything else is secondary, outline, ghost or link.
• One navy region at most per view (login brand panel, the Home hero, tooltips, toasts, the user's chat bubble).
• One highlight chip per card at most; three status tones visible at once at most.

What the contrast means in practice

• On a light ground a button is action blue with a white label (6.1:1), 8 px radius, one per view. White text on Varış Mavisi is 3.2:1, so it is for text of 24 px or larger (or bold 18.66 px or larger) and for graphics only.
• Varış Mavisi is never text on Krem or Beyaz (2.8:1 and 3.2:1), and never a button fill on a light ground. Links and inline accent text on light grounds are action blue #2A5BC8, underlined (5.4:1 on Krem, 6.1:1 on Beyaz). Derin Mavi is 9.8:1 but only 1.5:1 against navy body text, so a Derin Mavi link would look like plain text; it stays for headings and dark cards.
• On navy, white text is the default and Varış Mavisi text is fine (5.2:1). The button there is Varış Mavisi with a navy label (5.2:1). On Derin Mavi the accent falls to 3.5:1: large text and graphics only.
• Focus: buttons, links, chips, tabs and nav items show a 2 px navy ring with a 2 px offset (white on navy; the browser draws it for the keyboard only). Text fields turn their border action blue #2A5BC8 (6.1:1 on white) with a soft 3 px ring, because a text field matches :focus-visible on a mouse click too and an offset frame on every click is heavy. Varış Mavisi alone is under 3:1 on light grounds.

Product tokens · derived for UI, not brand colours

These tokens live in tokens.json (section 14) and are derived from the brand colours for interface use. They are not part of the identity: do not use them in a logo, an icon or a print identity piece. This guide's own Krem page keeps its warm hairline #E4DDD0, a brand-surface line; the product never uses it. Every ratio on this page is computed with the WCAG 2.2 formula.

WCAG 2.2 contrast, real pairings

Status colours · one pill, one set of tones

Inks on their soft grounds: success 5.2:1, warning ink 7.0:1, destructive ink 6.9:1. The tones are muted on purpose, so the action blue stays the only bright colour on a screen. Every status carries a word as well as a colour; green and red also differ in lightness, so the pills survive colour blindness. Red is only for failure and irreversible actions, never for prices, discounts or emphasis. Amber means someone has to act; if nobody does, it is not amber.

Fails, never use

The two Varış Mavisi pairs at 3.2 and 3.5:1 pass only as text of 24 px or larger (bold 18.66 px or larger) and as graphics such as the icon ring. Floors for everything else: text 4.5:1; control borders, focus rings and meaningful icons 3:1.

Light and dark grounds

The button changes with the ground: action blue with a white label on light grounds, Varış Mavisi with a navy label on navy. Never put action blue on navy, and never Varış Mavisi as a fill on a light ground.

Scale · 12 / 13 / 14 / 16 / 18 / 22 / 28 / 36

The floor is 12 px and there are no arbitrary sizes: pick the nearest step. This is the product scale. Brand surfaces such as this page's cover may set Poppins 600 headlines larger.

Families and usage

Tracking: display titles −0.02 to −0.01 em, body 0, eyebrows +0.06 em. Turn on font-variant-numeric: tabular-nums for prices, dates and times. No all-caps headlines; uppercase is for 12 px eyebrows and table headers only, and Turkish labels are better left in sentence case (section 7).

Turkish glyph test

Check the dotted capital İ, the dotless ı, ğ, ş and ç in every new face, weight and fallback. A fallback font that lacks them will silently swap in Latin letters and "Iğdır" will lose its meaning.

Prices, dates and codes

• One price format everywhere: the currency's sign first, in the reader's number format: ₺4.620,00 in Turkish, ₺4,620.00 in English; € $ £ the same way. Never the ISO code (TRY 4,620.00) and never "TL" (decision 2026-10-14). Set it in price-lg or price. Do not mix fonts for the same number on one screen.
• Tabular figures for prices, dates and times, so columns align and totals do not jitter.
• Mono is for machine codes only, so a PNR or passport number reads as something to copy exactly.

No italic accents in the product

Product UI has no italic accents and no italic blue names. A marketing headline may set one accent word in Varış Mavisi on navy, in colour only, never in italics. Colour a word only when it is interactive, a status or this one marketing accent.

Self-hosting

The marketing site and the product serve WOFF2 files from their own origin. Google Fonts is used only in previews like this page. Subset to Latin plus Latin Extended-A (which holds the Turkish letters) and preload the weights that appear above the fold. The product uses Inter 400, 500 and 600, Poppins 500 and 600, and IBM Plex Mono 500.

@font-face {
  font-family: "Inter";
  src: url("/fonts/Inter-Regular.woff2") format("woff2");
  font-weight: 400;
  font-style: normal;
  font-display: swap;
  unicode-range: U+0000-00FF, U+0100-017F, U+2000-206F, U+20BA,
                 U+2122, U+2190-2193, U+2212;
}

font-display: swap shows the fallback immediately and swaps when the file arrives. Poppins is wide, so size its fallback with size-adjust to keep the swap from moving the layout. U+20BA is the Turkish lira sign, U+2122 the ™ sign, U+2190–2193 the arrows (as in "İstanbul → Berlin") and U+2212 the true minus sign.

Fallback stacks

--font-display: "Poppins", system-ui, sans-serif;
--font-sans: "Inter", system-ui, -apple-system,
             "Segoe UI", sans-serif;
--font-mono: "IBM Plex Mono", ui-monospace,
             monospace;

Each fallback is a system face on at least one platform and covers Turkish. Do not add any face that fails either test. In email signatures and Office documents, where web fonts do not load, use Arial.

The link for previews: Inter 400, 500 and 600, Poppins 400, 500, 600 and 700 (this page also sets Poppins in its brand-surface specimens), and IBM Plex Mono 400 and 500 from Google Fonts. All three families are open source (OFL).

Principles

1. Say what happened, then what happens next. "Onaya gönderdim. Yöneticiniz onayladığında bilet gelir."
2. Numbers are facts. Prices, times and limits are stated exactly; never "around", never invented.
3. Policy is explained, not enforced in silence. Every exception says which rule and by how much.
4. The agency is always a person. Name it. "Acenteniz Gezi Tur bilgilendirildi."
5. One question at a time. If Turleno must ask, it asks one thing, then stops.
6. Never sell inside the product. No upsell copy in chat, receipts or notifications.

We say / we don't say

Microcopy

Naming rules

Tone by channel

Writing rules

Money: the sign first, no space, always two decimals; in Turkish a dot for thousands and a comma for decimals, in English the reverse. Never "TL" after the amount, never "4.120 TL", never the ISO code ("TRY 4,120.00"). Ranges use an en dash with no spaces. Price components in the product (cards, tables, totals) use the same format as sentences, in every language (section 6).

Turkish rules

• Suffixes take an apostrophe after a proper name: Turleno'ya, Turleno'nun, THY'nin, Gezi Tur'un.
• Mark the language. Every element holding Turkish carries lang="tr", so the browser cases, hyphenates and reads it aloud as Turkish.
• Uppercase in code with the Turkish locale. Use toLocaleUpperCase('tr-TR'). Without it "iş" becomes "IŞ" and "İstanbul" becomes "ISTANBUL".
• Prefer not to set Turkish in capitals at all. Sentence case is safer and reads calmer.
• Design around Turkish length. Turkish strings run longer than English ones; lay out buttons, pills and headers for the Turkish text first.

'iş'.toUpperCase();                // "IŞ"   wrong
'iş'.toLocaleUpperCase('tr-TR');   // "İŞ"   right

Bubble spec

Chat text is 14 px / 20 px Inter in the product and 16 px in marketing mockups. Timestamps and the footer line "Gezi Tur · Powered by Turleno" (agency first) are 12 px Navy 70 (#4A5A73, 6.6:1 on the #F7F8FA canvas) under the last bubble. Inter throughout, with IBM Plex Mono only for a PNR or another machine code.

Policy labels

This is the one status pill used for every status: 24 px tall, a 6 px dot and a sentence-case word in 13 px Inter Medium, full radius, no border, no icon. The pill sits at the start of the option line, before the carrier and time. Never colour the whole option row; the pill is the only coloured element. In policy is green, not blue, so a status never gets confused with an action.

Rendered conversation

AI disclosure

The first message of every conversation, on every channel, says what Turleno is and whose it is:

The chat header carries "Yapay zekâ asistanı" permanently, not only on the first screen. Nobody talking to Turleno should be able to believe they are talking to a person.

Why: Article 50 of the EU AI Act, which applies from 2 August 2026, requires people to be told when they are talking to an AI system. Turleno's core application infrastructure is hosted in the EU (Frankfurt), so we follow it in every market, Türkiye included.

Assistant accessibility

• The conversation is a role="log" region with aria-live="polite", so new messages are read out without interrupting.
• Each bubble starts with a visually hidden speaker label, "Turleno:" or "Siz:", so the conversation makes sense without its layout. The avatar is decorative.
• The typing indicator is announced once as "Turleno yazıyor", not on every dot.
• The logo's alt text is "Turleno"; the lockup's alt text is "Powered by Turleno".
• A confirmation carries a tick plus the word "Onaylandı". Colour never carries a state alone.
• Chips are real buttons with a 2 px navy focus ring and a 2 px offset.
• Target WCAG 2.2 AA, including tap targets of at least 24 × 24 px for every option, button and link in the chat.

Route line

The origin is a short navy bar, the same shape as the crossbar of the "t". The route is a single 2 px navy line, curved once, ending in the ring in Varış Mavisi. A policy check or approval on the way is a small Derin Mavi tick in a white dot. One route per composition. Never a globe, never an arc over a map, never dotted.

The ring as a shape

The ring is the only other graphic device. It can be cropped by the edge of a panel, scaled up as a backdrop in Varış Mavisi on navy, or drawn small in white. It keeps its proportions (about 10 % thick, open centre about 20 % across); it is never filled solid, outlined or given an effect.

Icon style

Outline icons with a 1.5 px stroke at 16 or 20 px (the app uses Lucide), round caps and joins, no fills. They take the text colour: Navy 70 when idle, action blue when selected, success green only for a completed state. Hotel ratings are filled stars in #B0620A followed by the number as text. One weight and one size family; no duotone, no filled variants, no icon inside a coloured circle.

Illustration ban list

• Planes, plane silhouettes, contrails, take-off arcs
• Globes, world maps, maps with pins, dotted arcs across continents
• Suitcases, passports, boarding passes, tickets with perforations
• Robots, sparkles, "AI" glows, neural-network dots and lines, brains
• Purple-to-blue gradients, glassmorphism, 3D blobs
• Gradients, shadows, glow or 3D effects on any of our marks
• Left-border accent stripes on cards and notices, shimmer loaders, italic accent words in the product
• Stock photos of people in airports or shaking hands
• Nazar beads, tulips, Bosphorus skylines, any "Turkishness" prop
• THY red and white, Pegasus yellow and red
• Emoji anywhere in the interface or in marketing

If a page needs a picture and a route line or the ring does not fit, use a framed product screenshot instead. Real screens beat any illustration for this audience.

Photography stance

Framing product screenshots

Tokens

The ring, arrived

When a booking or an approval completes, the confirmation card shows the ring drawing itself in Varış Mavisi over 600 ms, then a navy tick in its centre. It plays once per completed action and never loops. The state is also in words ("Onaylandı"), so the movement is never the only signal.

Reduced motion

Under prefers-reduced-motion: reduce, every movement becomes a fade of 120 ms or less. Nothing rises, slides, draws or scales: the ring simply appears.

The typing indicator stops animating and stays static, with the screen-reader text "Turleno yazıyor" carrying the state. Loading follows the same rule: skeletons and spinners stop, the ring appears already drawn, the progress bar is static, and the status line keeps carrying the meaning.

The logo in motion

The logo animates in one place only: the end card of a video. The "o" arrives, rising 8 px into place and fading in over 320 ms, then the whole mark holds still for 2 s. It never loops, spins, bounces or appears as a loading spinner, and agencies may not animate it (section 4).

Loading

Respect prefers-reduced-motion everywhere. Content already known (the route, the dates, the filters) stays real text during a search, never a skeleton.

App start

A light screen, so there is no dark flash before the light app shell. The icon's ring draws once in 900 ms; the status line steps through what is happening ("Çalışma alanınız hazırlanıyor", "Seyahatleriniz yükleniyor", "Seyahat politikanız denetleniyor"); the agency's logo and name sit above the bar and "Powered by Turleno" at the foot.

Search and button

The progress card is a live region: done steps get a green dot, the current step an action-blue dot, pending steps a grey one. Skeletons are muted blocks at the real content's size, pulsing between full and half opacity. The busy button keeps its label and shows a 16 px spinner.

Source and readme

Turleno_Marka_Kimligi_v1.0.pdf: the five-page source identity (Marka Kimliği v1.0). Where this guide and the PDF differ on a logo, colour or usage rule, the PDF wins.

README.txt: file list, colour values, rules and the trademark line, in Turkish and English.

How the files are made

All logo files are generated from one source module, docs/brand/source/turleno-marks.mjs, by npm run brand:assets. The same run writes the favicons and the in-app marks. A hand-edited copy of the path data anywhere else is a bug.

Inside the ZIP the files sit in folders; on this page, and on the server, they are flat.

File naming

Lowercase, hyphens, no version numbers in file names; the version lives in this guide. The colour word in a name describes the colourway, not the ground. Vector first, PNG only where a channel refuses SVG.

Requesting more

The files above are the current kit, published at turleno.com/brand. Agencies get a separate co-brand pack with the "Powered by Turleno" lockups pre-built in both colourways, so nobody assembles one by hand. Anything not in the kit goes to brand@turleno.com.

Trademark line

Turleno ve halka logosu Turleno'nun ticari markalarıdır. Diğer tüm markalar sahiplerine aittir.

Turleno and the ring logo are trademarks of Turleno. All other marks belong to their owners.

Use ™ after the first prominent "Turleno" in legal footers and printed material until the TÜRKPATENT registration is granted. Use ® only after the registration certificate is issued, never before. The line goes in the footer of the website, of decks and of the asset kit's readme, and at the foot of this guide.

Third-party marks

Airlines, Travelport, Enterprise, WhatsApp, Slack and Microsoft Teams are written as plain text in running copy. Their logos appear only with the owner's official file and permission, never recoloured and never larger than our own mark.

THY, Pegasus, AJet ve diğer markalar sahiplerine aittir.

Put that line under any page, slide or brochure that names a supplier or a channel.

Ownership and review

• Owner: Burak Gazioğlu.
• Changes are proposed as a pull request to the guide's source and approved by the owner.
• Any change to the logo or to a colour needs a second reviewer as well, and goes through turleno-marks.mjs and npm run brand:assets, never a hand-edited file.
• Product tokens (colour, type, radius, states) change in tokens.json first (docs/design/turleno-v2.1-handoff/tokens.json), never in code or on this page. apps/web/src/__tests__/design-tokens.test.ts enforces that the app matches it and that the contrast floors hold. This page follows the file.
• General questions go to hi@turleno.com; brand requests and new placements go to brand@turleno.com.

Version numbers

• Major (x.0): any change to a mark or a colour.
• Minor (2.x): new rules.
• Patch (2.1.x): fixes to wording, values or specimens.

After a major release, old assets stay valid for 90 days. After that, only files from the current kit may be used. Files from versions before 2.0 are no longer valid.

Changelog