I wrote a manuscript in vim a couple Novembers ago, for NaNoWrimo. I used a couple plugins, primarily Goyo [1] to add some margins, but otherwise, yeah, plain vim. I don't think it was really any more productive than my current workflow in Obsidian. Vim keybindings are more useful for editing than for writing (and for editing code in particular, where the changes you're making are much more structured). Also,... - Source: Hacker News / 10 months ago

I have created full on programs to systematically created screenshots with the game emulators with RetroArch. Also an automation tool to use a preexisting program named chdman that converts files into a needed format (also unpacking from archives). A little Python script to create a recents list of files for Vimwiki. I also created a program to access 🌈 emojis 🌈. I wrote my own GE Proton downloader and manager.... Source: about 1 year ago

I use VimWiki inside of Neovim, with additional Plugins/configurations. Lightweight and let's you use the power of (Neo)Vim. Source: over 1 year ago

Well, Zettelkasten looks to me much like wiki. And standard wiki solution for vim is https://vimwiki.github.io/ and it should work quite well for you. Also, it is all plain text files so conversion should not be that difficult. Source: over 1 year ago

I end up taking linear notes in a text file, with un-resolved or in-progress items at the bottom. They get pushed downward linearly until they are finished, at which point they get immortalized in the greppable daily log above. Requires a lot of discipline and doesn't have a lot of structure, but having the "working area" next to the journal has served me well. I use vimwiki[1] for most of the editing, in addition... - Source: Hacker News / about 2 years ago

I have used Markdown before (https://dillinger.io/) so wouldn't have a problem with using it again as long as on page SEO isn't any extra effort. I am not sure how I would use Markdown and then add the content to the blog to be deployed and if that is going to be much harder than a headless CMS, I would go for the headless. Source: 7 months ago

Useful rescources for this are: Markdown Cheatsheet and Markdown Editor. - Source: dev.to / about 1 year ago

-put chatgpt output into dillinger.io and save as markdown file. Source: about 1 year ago

Did you try pasting the response in a Markdown editor and check if it's working? Here's one online - https://dillinger.io/. Source: about 1 year ago

Which works at https://dillinger.io/, but not https://insiders.vscode.dev. Source: about 1 year ago