How can I suggest features or share my Obsidian plugins and themes on the forum?

Updated

The Obsidian Forum routes each kind of contribution to a specific category, and picking the right one is most of the work. Core feature suggestions go to Feature requests, third-party plugin ideas go to Plugins ideas, and finished work — plugins, themes, CSS snippets, workflows, templates — goes to Share & showcase. Theme and CSS development questions have their own developer category. The sections below cover what belongs where, how voting works, and what to check before you post.

Suggesting a feature for core Obsidian

Post in the Feature requests category when you want something added to Obsidian itself, not to a community plugin.

Two things to know before you write:

  • Likes are votes. The forum states plainly that "Likes (Hearts) = Votes," so a suggestion's support is measured by hearts rather than by replies. A short, clear request that people agree with can outrank a long thread.
  • Search for duplicates first. The category description asks you to "try searching the forum for duplicates before posting." If a thread already exists, adding your heart and a comment is more useful than starting a parallel one.

If your idea is really about a third-party plugin rather than core Obsidian, it belongs in Plugins ideas instead — see below.

Sharing a plugin idea vs. a finished plugin

These are two different categories, and mixing them up is the most common misfile.

What you have Where it goes
An idea for a third-party plugin you'd like someone to build Plugins ideas
A completed plugin you built Share & showcase
A completed theme Share & showcase
A CSS snippet, workflow, or template Share & showcase

The Plugins ideas category is described as a place to "share ideas for third-party plugins you would like to use." Its description also notes that implemented plugins "should open a thread in Share & showcase" — so once an idea becomes real code, it moves.

Share & showcase is the home for finished work of any kind: "Showcase your plugins, themes, CSS snippets, workflows, templates, and nifty hacks." If you've built something and want people to use it, this is the destination.

Getting help while building a theme or plugin

If your work isn't finished yet and you're stuck on the technical side, there are dedicated developer categories:

  • Devs: Plugins & API — for the plugin interface and technical questions while working with Obsidian. The category points to the Dev Docs and a #plugin-dev channel on Discord. Note that questions about inclusion in the community directory are handled in a separate Discord forum, and completed plugins still go to Share & showcase.
  • Devs: Theme Design & Custom CSS — for designing themes and snippets with CSS, with a #theme-dev channel on Discord. Completed themes also go to Share & showcase.

So the pattern is: ask development questions in the Devs categories, then post the finished result in Share & showcase.

Before you post anything

A few habits save you and everyone else time:

  1. Search first. Both Feature requests and Bug reports explicitly ask you to check for duplicates.
  2. Read the relevant guide. The Help category points to the User Guide, and Bug reports points to the Troubleshooting Guide. There are separate forum sections for API and CSS questions.
  3. Match the category to the artifact. Idea → Plugins ideas. Finished → Share & showcase. Core suggestion → Feature requests. Development question → the matching Devs category.
  4. Use hearts as votes. If you support an existing feature request, like it rather than posting "+1."

If you'd rather chat than post, the forum notes there's a Discord channel for general help, plus the #plugin-dev and #theme-dev channels for development topics.