P5.1 · Launch: README, screenshots, community-plugins submission

What

Everything needed to get the plugin in front of users.

Deliverables

• README.md: hero GIF, 3-sentence pitch, feature list, install steps (pre-community-approval: "download the latest release, drop into .obsidian/plugins/"), settings walkthrough with screenshots, free vs Pro table, privacy note ("your API key never leaves your machine").
• 30-second demo GIF: record a pull + edit + push cycle.
• Static screenshots for Obsidian community-plugins directory (1440×900, 4 total).
• Plugin manifest in the repo: manifest.json with id, name, version, minAppVersion, description, author, authorUrl, fundingUrl.
• versions.json keyed by Obsidian compatibility.
• GitHub release with built main.js, manifest.json, styles.css.

Submission

1. Fork obsidianmd/obsidian-releases.
2. Add an entry to community-plugins.json per their PR template.
3. Submit PR. Wait 3–14 days for review (bot + human).
4. On merge → plugin appears in Obsidian's in-app Community Plugins browser.

Launch posts

• r/ObsidianMD: "I built a Linear sync plugin (+ free version available now)"
• Obsidian Discord #plugin-showcase
• Indie Hackers milestone post
• Twitter/X thread tagging Linear's official account

Acceptance criteria

• Community-plugins PR submitted.
• 3 launch posts live within 48h of PR merge.
• At least one screenshot and one GIF embedded in the README.