u/Big_Local3239

This new plugin opens .docx files natively within Obsidian and saves edits directly back to the file inside the vault.

Sorry to put another plugin up for discussion so soon, but as far as I know, there has been no way so far to actually EDIT docx files directly inside Obsidian (whereas preview and conversion is of course possible); so I thought, i could try to solve that problem for myself, because I'd like to as much textwork as possible in Obsidian. The whole thing is just a a sketch, at this point; please be gentle with the critique.

Opening any .docx file from the file tree will route it to a custom file view. You can then use the editor toolbar's save action in the upper left corner to write your changes back to the file.

Additionally, the plugin supports embedding docx files as read-only components inside your regular Markdown notes using the standard ![[filename.docx]] syntax. There's still a lot to do there, though.

The plugin is not yet part of the official community list, but you can test it during this beta phase in two ways. The easiest method is via BRAT by simply adding the repository URL as a beta plugin. Alternatively, you can install it manually by downloading main.js and manifest.json from the latest release and copying them into your vault's plugin folder.

https://github.com/kpaede/docxidian

Please feel free to test it out, and let me know if you run into any major issues. I might get back to it next week, to work on it again.

Disclaimer: I vibecode my plugins, and the technical scope of this project honestly exceeds my actual programming skills. Because of this, there is always a residual risk when using it, so please keep that in mind. I build these tools primarily to bridge very specific gaps in my own research and writing workflow. Should this plugin ever become completely obsolete because a professional developer takes the idea and builds something truly solid and sophisticated, I would be absolutely thrilled.

Hey everyone, I vibe coded a tool for for my literature excerpting, which is basically a drag-n-drop mindmap editor for text (and not just for headings). The thing is a personal proof-of-concept and the scope of this project honestly exceeds my formal programming skills. I would very much love if it became obsolete because of something substancial as an alternative.

I would love for people to try it (please with a backup of your files) out and give feedback, but my ultimate goal is to inspire a professional developer to take this concept and build a truly solid, sophisticated version of something between Marginnote and Lineage as an Obsidian plugin.

What It Does: The Excerpt-Outline-Mindmap-Editor lets you visually structure text excerpts as mindmaps using a drag-and-drop interface. The underlying data model is standard Markdown outline (an indented list). This means it uses no proprietary format or hidden metadata, making it completely native and fully compatible with Obsidian's default editor and outline plugins like Lineage.

The plugin features a visual drag-and-drop system where dragging a parent node automatically relocates its entire hierarchical subtree. Nodes fully render standard Markdown content, including links, images etc.

To keep editing efficient, it asks before deletion ( whether to wipe the whole subtree or keep the children), there is also multi-node selection, spatial keyboard navigation, and standard clipboard shortcuts (Cut/Copy/Paste/Duplicate). Additionally, you can embed read-only mindmaps into other notes via a custom code block, or add a frontmatter key to force files to open in the mindmap view automatically.

If you want to test it, the repository is available here:
https://community.obsidian.md/plugins/excerpt-outline-mindmap-editor
https://github.com/kpaede/Excerpt-Outline-Mindmap-Editor

Hey guys, I’m currently vibecoding (beware!) an Obsidian plugin that allows you to edit SVG files. For my own work, I often deal with musical notations in SVG format and needed a way to annotate them—ideally in a way where I can remove the annotations later. (Since SVG allows for non-destructive editing.)

Disclaimer: Since I am vibecoding this, the code quality will most certainly be questionable and it comes with certain risks, which is why I’m labeling it as such.

It’s still in the very, very early stages, so use at your own risk. But I’ve made some decent progress and wanted to put it out there for discussion, as lots of stuff already works pretty okay'ish.

The goal is quite simply an implementation of https://github.com/svg-edit/svgedit . All the work and credit belong to its developer, and that will, of course, be properly credited on GitHub. I’d love to hear your thoughts on how this could be developed further.

Install it via the community plugins https://community.obsidian.md/plugins/svgeditor
oder from Github https://github.com/kpaede/svgeditor