See the icon
in context.
Practical examples showing how the Cortlet icon should appear in websites, repositories, integrations, attribution, and other compact digital contexts.
How to use these examples
Context matters.
The standalone Cortlet icon is most useful where space is limited or Cortlet is already clearly identified. These examples show when the icon works and when the full Cortlet identity may be more appropriate.
Keep context clear
The viewer should understand what the Cortlet icon represents.
Keep it intact
Use official assets without recoloring, stretching, rotating, or rebuilding the mark.
Keep it appropriate
Use the full Cortlet logo when the brand name needs to be explicit.
Example 01 // Website navigation
Website navigation
The Cortlet icon can be used in compact navigation when the Cortlet identity is already clear from the surrounding context.
Keep the icon at a clear, readable size.
Maintain the icon's original proportions and clear space.
Use the full Cortlet logo when the brand name is not otherwise obvious.
Developer infrastructure
Compact identity.
Clear context.
The icon works here because the Cortlet name appears directly beside it and the mark remains visually clear.
Context
The Cortlet name appears beside the icon, so the identity is immediately clear.
Scale
The icon is large enough to remain recognizable without dominating the navigation.
Unmodified
The official icon is used without recoloring, distortion, cropping, or decorative effects.
Example 02 // Third-party attribution
Third-party attribution
When another product references Cortlet, the Cortlet icon should remain clearly secondary to that product's own identity.
Keep the host product's identity visually dominant.
Pair the icon with accurate descriptive wording.
Do not imply that Cortlet owns, operates, certifies, or endorses the third-party product.
ACME Developer Platform
Built for realtime
developer workflows.
ACME remains the clear primary identity while Cortlet is referenced only where relevant.
Secondary
ACME remains visually dominant while Cortlet is used only as supporting attribution.
Descriptive
The wording explains Cortlet's role without overstating the relationship.
Independent
Nothing suggests that Cortlet owns, certifies, or endorses ACME.
Example 03 // Repository avatar
Repository avatar
The standalone Cortlet icon works well for repositories, developer projects, and organization avatars where the available space is compact and usually square.
Use the official icon rather than squeezing the full horizontal logo into a square avatar.
Keep enough padding around the mark so it remains clear at small sizes.
Keep the project or repository name separate from the icon rather than adding text inside the asset.
Cortlet-Org
cortlet-example
A fictional developer project showing how the Cortlet icon can be used as a compact repository identity.
Language
TypeScript
License
MIT
Status
Active
cortlet-example
Example repository documentation. The repository name stays separate while the official Cortlet icon provides the compact visual identity.
Compact
The standalone icon fits naturally into the square space used for repository and organization avatars.
Readable
The mark has enough surrounding space to stay recognizable even at smaller rendered sizes.
Separate
The repository name remains real text rather than being added inside or around the Cortlet icon.
Example 04 // Integration tile
Integration tile
The Cortlet icon works well inside integration directories, product grids, and compact technical cards where the product name is displayed separately.
Keep the icon and product name as separate elements.
Give the icon enough room to remain recognizable inside the tile.
Match the visual weight of surrounding integrations rather than making Cortlet disproportionately prominent.
ACME integrations
Connect your stack.
A fictional integrations directory showing Cortlet alongside other tools with equal visual treatment.
Cortlet
Realtime infrastructure
Neon
Database
Vercel
Deployment
Resend
Balanced
Cortlet receives the same visual treatment as the other integrations instead of being promoted above them.
Readable
The icon is shown at a practical size with enough surrounding space to remain recognizable.
Separated
The official icon stays intact while the product name and description remain normal interface text.
Example 05 // Incorrect usage
Modifying the icon
Keep the Cortlet icon exactly as provided. Changes to its proportions, color, orientation, or visual treatment can weaken recognition and create inconsistent brand usage.
Use official light, dark, or transparent assets.
Scale the icon proportionally.
Keep the icon free from decorative effects and surrounding clutter.
Don't stretch
Never change the icon's original proportions.
Don't recolor
Do not create unofficial icon colors.
Don't rotate
Keep the official orientation of the mark.
Don't add effects
Avoid shadows, glow, outlines, bevels, or other treatments.
Don't crop
The complete mark should remain visible.
Don't crowd
Keep unrelated content outside the icon's clear space.
Use the asset as provided.
Keep the original geometry, orientation, proportions, and visual treatment. Choose the official variant that works best for the background instead of modifying the mark.
Recognition
Consistent geometry makes the Cortlet icon easier to identify across different products and interfaces.
Consistency
Official variants keep the icon visually consistent instead of creating competing versions of the mark.
Clarity
Clear space and simple treatment prevent surrounding content from interfering with the icon.
See everything
working together.
Open a complete fictional website showing the Cortlet icon used inside navigation, interface elements, and supporting attribution.
Quick summary
Compact.
Clear.
Cortlet.
Use the standalone icon when space is limited.
Keep Cortlet clearly identified through nearby text or surrounding context.
Preserve the icon's original proportions, orientation, and visual treatment.
Keep the icon visually secondary when used inside a third-party product.
Use the full Cortlet logo when the brand name needs to be explicit.
Continue exploring