mark-when
Support for other editors/local editting
I'm going to try to use this issue to keep track of requests for local development and support in other tools. If one path becomes more apparent or gains more momentum than others I'll break it back out into its own issue.
Right now I'm seeing a few common requests:
- [ ] Obsidian.md
- [ ] VS Code
- [ ] Deploy locally (dockerize markwhen)
- [ ] CLI
In my current position (that is, having a full time job that is not markwhen (yet!)), I have to prioritize my time, and I think that priority should be the website, as it has the most reach and is the easiest for people to get started on.
However, I'm supportive of these other endeavors, though I won't be able to give them as much attention, at least right now.
I was thinking in the meantime the most helpful thing would be a CLI that takes a markwhen document and outputs HTML? That way people can do whatever they want with the html (host it themselves, etc) or potentially use it as the preview view in VS Code/Obsidian?
I want to enable everyone else but I also want to focus on the website for the time being.
VS code extension - it's quite basic right now (no editing from the timeline, only one page, no filtering) but it is a start
I'm going to take a stab at an Obsidian plugin and I plan to Support standard Markdown headings and other Obsidian/Markdown syntax
That would be great! Hopefully with traction, even GitHub will embrace it as well.
@huyz Check out the vscode branch, it might be helpful? It's just some commits on top of the main branch to make it work with vscode.
This is amazing, thank you. Is it a big stretch to add support for the different markdown editors e.g. Logseq?
Is this the place for VS code extension bug reports? I couldn't find anywhere else to put them. The issue I faced was that checking off subtasks in the Event detail view does not get stored in the plain text. As soon as I navigate away from the event view, the checkmark disappears and no change happens on the timeline.
