Managing Tool Listings

If you've claimed a tool on StackShare, you have access to manage its listing. This guide covers everything you need to know about optimizing your tool's presence.

Accessing Tool Settings

Once you've claimed your tool, you can access settings by:

1. Navigating to your tool's page
2. Clicking the Settings tab (visible only to tool owners)

General Settings

Tool Name & Description

Your tool's name and description are the first things developers see. Write a clear, concise description that:

• Explains what your tool does in one sentence
• Highlights key features and use cases
• Avoids marketing jargon - developers prefer straightforward explanations

Logo & Hero Image

Upload high-quality images:

Logo:

• Is recognizable at small sizes (favicons, list views)
• Has a transparent or solid background
• Represents your brand clearly

Hero Image:

• Displayed prominently on your tool's overview page
• Can be auto-captured from your website or uploaded manually

Links

Add important links to help developers learn more:

• Website - Your tool's homepage
• Documentation - Link to your docs

Categories & Classification

Layer Selection

Choose the layer that best represents where your tool fits:

• Application & Data - For frameworks, languages, databases, libraries
• Utilities - For testing, monitoring, analytics tools
• DevOps - For CI/CD, containers, infrastructure tools
• Business Tools - For productivity, communication tools
• AI - For ML frameworks, LLMs, AI tools

Category

Select the most specific category within your layer. Being in the right category helps developers find your tool when browsing.

Understanding Your Tool's Metrics

Your tool page displays several metrics that show community engagement:

• Stack count - How many stacks include your tool
• Followers - Users following your tool for updates
• Votes - Community votes on your tool

These metrics are displayed publicly and contribute to your tool's visibility in trending and search results.

Responding to Community

Stack Decisions

When developers write about why they chose (or didn't choose) your tool, these appear as "stack decisions." While you can't edit these, you can:

• Learn from feedback to improve your tool
• See common use cases and pain points

Pros & Cons

Community members submit pros and cons about tools. These are valuable signals about what developers appreciate and what could be improved.

Best Practices

Keep Information Current

• Update your description when major features launch
• Keep links working and current
• Update the logo if your branding changes

Engage Authentically

• Don't spam or self-promote excessively
• Let your tool speak through real user testimonials
• Focus on helping developers succeed

Leverage Social Proof

• Encourage satisfied users to add your tool to their stacks
• Ask users to share their stack decisions
• Highlight notable companies using your tool (if they've made it public)