An Intro to Making Logseq Plugins ft. Sawhney

Logseq plugin development is presented as a practical, learn-by-doing path: start from existing open-source plugins, modify them until they work for a real need, and use quick feedback loops (console logs, small changes, rebuilds) to gradually build confidence. The session’s core message is that coding experience isn’t a prerequisite so much as a willingness to understand basic programming concepts (functions, variables, loops) and then iterate on working examples—especially because Logseq’s plugin ecosystem is open and accessible.

Ariane Sany (a Logseq power user) traces his entry into plugins to a gap he felt in earlier note-taking tools. After using Notion—particularly its templator blocks for repeated and dynamic content—he found Logseq covered “a ton of stuff” but lacked that specific templating workflow. ClojureScript, the language behind Logseq’s codebase, initially felt daunting, and bug-fixing attempts stalled. Plugins became the easier route to contribute features he wanted, while also helping others who might need similar functionality.

To learn plugin basics, he recommends using the Logseq sample plugins repository on GitHub as a primary reference. He chose a Pomodoro timer plugin as a close starting point for his own “template plugin” idea, then treated the code like pseudo-code—reading line by line, identifying what each part does, and experimenting by changing or deleting functions. He emphasizes that learning doesn’t require mastering everything upfront; it’s enough to know how code runs at a conceptual level, then translate that thinking into JavaScript. His approach also leans heavily on “scratch your own itch”: pick a feature you wish existed, then build it rather than waiting for the core team.

The session then moves into a live walkthrough of setup and execution. Ariane uses Visual Studio Code and a GitHub template for Logseq plugins, highlighting the three key files: index.html (entry point), index.js (plugin logic), and package.json (metadata and build configuration). Running yarn installs dependencies, and yarn build compiles the plugin into a dist folder that Logseq can load. In Logseq, developer mode must be enabled, then the plugin can be loaded via “Load unpack plugin.”

A simple starter plugin demonstrates the lifecycle: Logseq runs initialization code, registers commands (slash commands), and triggers a function that inserts blocks. From there, the tutorial builds a new plugin from scratch: a right-click context menu item that converts the selected block’s text to uppercase. The implementation proceeds in stages—first confirming the block UUID arrives correctly, then retrieving block data (noting that calls return Promises and require await), then computing uppercase text, and finally updating the block via the editor API. The walkthrough also surfaces best practices: rely on IDE autocomplete, consult Logseq’s plugin documentation and source code when docs are unclear, and use console logging after each step to verify behavior.

By the end, the conversation broadens into learning strategy and community resources. Ariane points to javascript.com for a fast JavaScript foundation, Stack Overflow for targeted questions, and the Odin Project for deeper practice. He also argues for documentation improvements—more plain-English explanations and concrete examples per API function—because newcomers can feel overwhelmed. The session closes with encouragement to use the Logseq Discord (especially plugin developer channels) and to propose a “pain point” plugin as homework, reinforcing that the fastest path to skill is building something useful, even if the first version is messy.