Skip to main content
Neon Postgres Docs
current

Search documentation

Type to search this documentation.

On this pageOverview

Component icon guide

A comprehensive guide to all icon systems used in Neon documentation. This guide helps you understand which icon system to use and how to implement them correctly. How to choose the right icon system ...

A comprehensive guide to all icon systems used in Neon documentation. This guide helps you understand which icon system to use and how to implement them correctly.

  • How to choose the right icon system for your use case
  • Which icons are available in each system
  • How to implement icons correctly in components
  • Best practices for icon usage and troubleshooting

Neon documentation uses multiple icon systems for different components. Understanding which system to use is crucial for proper implementation.

  1. TechCards Icons - Colorful technology logos and framework icons
  2. DetailIconCards Icons - Monochrome feature and service icons
  3. DocsList Icons - Simple navigation and action icons
Component Icon System Use Case
TechCards TechCards Icons Technology/framework showcases
DetailIconCards DetailIconCards Icons Feature/service showcases
DocsList Built-in themes Documentation links
MDX
<DetailIconCards>
  <a
    href="/docs/ai/openai"
    title="OpenAI integration"
    description="Build AI features with OpenAI"
    icon="openai"
  >
    OpenAI Integration
  </a>
  <a
    href="/docs/ai/langchain"
    title="LangChain integration"
    description="Create AI workflows with LangChain"
    icon="langchain"
  >
    LangChain Integration
  </a>
</DetailIconCards>

For technical implementation details, see the Icon Systems section in the Component Architecture guide.


  • TechCards: Use for technology and framework showcases
  • DetailIconCards: Use for feature and service showcases
  • DocsList: Use built-in themes for documentation links
  • TechCards: Use kebab-case (for example, node-js, next-js)
  • DetailIconCards: Use camelCase or kebab-case as defined in the mapping
  • File Requirements: Ensure SVG files exist in the correct directories
  1. Test your icons: Always verify that your chosen icon works in the target component
  2. Check both systems: If an icon doesn't work in one system, try the other
  3. Use descriptive names: Choose icon names that clearly represent the technology or feature
  4. Document your choices: Keep track of which icons work in which components
  5. Fallback gracefully: Provide alternative text or descriptions when icons aren't available

Use Case Component Icon System Example
Technology showcase TechCards TechCards Icons Node.js, React, Python
Feature showcase DetailIconCards DetailIconCards Icons OpenAI, AWS, Database
Documentation links DocsList Built-in themes Guides, API docs
Simple navigation DocsList Built-in themes Related topics

  1. Icon not displaying: Check that the icon name exists in the correct system
  2. Wrong icon system: Verify you're using the right component for your icon
  3. Missing files: Ensure SVG files exist in the correct directories
  4. Case sensitivity: Icon names are case-sensitive

To test if an icon works:

  1. TechCards: Check if {icon}.svg exists in /public/images/technology-logos/
  2. DetailIconCards: Check if the icon is mapped in the component code
  3. DocsList: Use the built-in themes (default, docs, repo)
  • Review the Component Architecture for technical details
  • Test icons in a development environment before using in production


This guide provides an overview of Neon's icon systems and usage guidelines. For complete icon listings and detailed examples, refer to the Component Guide.

  • TechCards uses colorful technology logos from /public/images/technology-logos/
  • DetailIconCards uses monochrome feature icons mapped in component code
  • DocsList uses built-in themes for simple navigation
  • Always test icons in the target component before using
  • Choose the right component based on your use case, not just the icon availability
Suggest an edit

Propose a replacement for this page. The site team reviews it before applying any changes.

Export
Documentation menu