Obsidian — Custom Plugins Part 1

With the plugin architecture of Obsidian, it gives you control over your data and a lot of control over the behaviour of the app itself. Obsidian was built to take advantage of open web technologies. That means that there is a lot of flexibility when opened up for anyone to manipulate and extend the way Obsidian works. I covered community plugins built by third parties and added them to the community directory of plugins. But that doesn’t mean you can’t create something yourself for your personal use.

Technologies

If you want to dive into creating your plugin or looking at how others work, there will be a few things helpful to know or learn. Since these aren’t unique to Obsidian, these are skills that could be helpful to you in many areas or modern technology.

Display — First, some understanding of HTML and CSS, the web’s basic building blocks, and how everything is displayed. This will be very useful if you want to change the look of things.

Programming — For functionality and programming, you want to look into Javascript and Typescript (a superset of javascript, basically a stricter form of Javascript).

Server — Some familiarity with Node.js will also help. This is the server technology (itself runs on javascript) and runs Obsidian under the hood, so you will need to ensure that it is installed on your machine to begin developing Obsidian plugins.

Data — Familiarity with JSON (JavaScript Object Notation) will also help. This is like the data storage version of javascript. You can think of it as your Markdown notes but for Javascript to read.

This post was created with Typeshare

--

--

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store