obsidotion

unlisted

by p32929

a simple obsidian plugin that syncs from/to obsidian/notion

โ˜… 36 starsUpdated 1y agoMIT
View on GitHub

obsidotion

A simple obsidian plugin that syncs from/to obsidian/notion. Works on all platforms

Screenshots

From windows

Screenshot (77)

From Android

Screenshot_20240525-161914_Obsidian

How to use

  1. Star the repo :P
  2. Install the plugin (see installation methods below)
  3. Follow this instruction: https://github.com/EasyChris/obsidian-to-notion/?tab=readme-ov-file#how-to-use

After that you can:

  1. Upload the whole vault to notion ( replaces remote data if already exists )
  2. Download the whole notion database to obsidian ( replaces local file if already exists )

How to install

Method 1: Download from releases (easiest)

  1. Go to Releases
  2. Download obsidotion-plugin.zip from the latest release
  3. Extract the zip file
  4. Copy the extracted folder to your_obsidian_vault/.obsidian/plugins/obsidotion
  5. Open obsidian and enable the plugin

Method 2: Manual build

  1. Star the repo :P
  2. Clone the repo inside your_obsidian_vault/.obsidian/plugins
  3. Go to the folder
  4. Run npm install or yarn
  5. Run npm run build or yarn build
  6. Open obsidian
  7. Enable the plugin

For developers who dont want to copy files manually every time

You can create a .env file to auto-copy the built files to your obsidian vault. This way you dont have to manually copy main.js, manifest.json, styles.css every time you build.

Create a .env file:

OBSIDIAN_VAULT_PATH=/path/to/your/obsidian/vault/.obsidian/plugins
PLUGIN_ID=obsidotion

If you dont provide the .env file, the build will still work fine. You'll just have to copy the files manually

License

MIT License โ€” Copyright (c) 2024 Fayaz Bin Salam. See LICENSE for the full text.

Contributing

Contributions are warmly welcomed and greatly appreciated! Whether it's a bug fix, new feature, or improvement, your input helps make this project better for everyone.

Before submitting a pull request, please:

  1. Create an issue describing the feature or bug fix you'd like to work on
  2. Wait for discussion and approval to ensure alignment with project goals
  3. Fork the repository and create your feature branch
  4. Submit your pull request with a clear description of changes

This approach helps avoid duplicate efforts and ensures smooth collaboration. Thank you for considering contributing!

Share

Sharing this repository with your friends is just one click away from here

facebook twitter tumblr pocket pinterest reddit linkedin whatsapp

Support

If you like my works and want to support me/my works, feel free to support:

buymeacoffee

Sponsor a mention โ€” $499 one-time: your name + link in this section for 3 months. $1,200 one-time: featured placement at the top of this section, plus a pinned mention on my X profile, for 3 months. Email fayazdevinbox@uberip.com for an invoice.


๐Ÿ’ผ Using this at a company?

I do fixed-price delivery work on my own projects. One invoice, one date, no hourly billing:

White-label build โ€” this project rebranded, extended and deployed as yours$6,500 ยท 3 weeks
Custom app from scratch on my own stack, signed and auto-updating$12,500 ยท 6 weeks
Production-hardening sprint โ€” 72 hours on this project, for your load and your security review$999
Ongoing capacity โ€” one project-week of my time reserved every month$9,000 / month

Full details โ†’ p32929.github.io/hire ยท Email fayazdevinbox@uberip.com โ€” scoping and quotes are free and I answer within one business day.

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.