SlideX

approved

by Noct

Send explicitly selected Obsidian notes to SlideX deck import jobs. - This plugin has not been manually reviewed by Obsidian staff.

28 downloadsUpdated 4d agoMIT

SlideX

SlideX is a desktop-only, read-only bridge between an Obsidian Vault and SlideX. You decide the folder, tags, dates, and files to share. The plugin sends only the selected import snapshot, referenced images, and later changes to notes you explicitly link to presentation elements in SlideX.

It does not run an AI model, index your full note content in SlideX, or write to your Vault.

Install from a release

After SlideX is listed in Obsidian Community Plugins:

  1. Open Settings → Community plugins.
  2. Search for SlideX and select Install.
  3. Enable SlideX, then select Connect SlideX from the ribbon icon.

Install locally for testing

Clone this repository, install dependencies, and provide the exact absolute plugin directory of a disposable test Vault:

npm ci
npm run install:local -- \
  --plugin-dir "/absolute/path/to/SlideX Test Vault/.obsidian/plugins/slidex"

Then restart Obsidian, open Settings → Community plugins, and enable SlideX. Re-run the command after rebuilding to update the local plugin. You must have Obsidian Desktop installed for the obsidian:// connection link to open.

Privacy and permissions

  • The plugin is desktop-only and does not modify notes, attachments, or Vault settings.
  • SlideX only receives an index of Vault metadata after you connect, then the Markdown and referenced images included by an import job you explicitly choose in SlideX Workspace. Automatic presentation sync reads only a linked note after its path changes; unlinked note contents remain local.
  • Connection tokens are scoped to one Vault connection and can be revoked from SlideX Workspace. Revoking stops new reads; it does not delete existing SlideX presentations.

Development

npm ci
npm run check

Release contents

Run the following before creating a GitHub release:

npm run release:prepare

It verifies the manifest and creates these exact release attachments in dist/release/:

  • main.js
  • manifest.json

Create a GitHub release whose tag is exactly the version in manifest.json, then attach those two files. Keep this source repository's README.md, LICENSE, manifest.json, and versions.json committed at its root before submitting it to the Obsidian Community directory.

For plugin developers

Search results and similarity scores are powered by semantic analysis of your plugin's README. If your plugin isn't appearing for searches you'd expect, try updating your README to clearly describe your plugin's purpose, features, and use cases.