-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Look at related projects #6
Comments
Not completely relevant, but obsidian.md is an Electron app which sits on top of a local folder of (markdown) files. We could take inspiration from it. |
Two more related projects: Substance.io Looks like there is some overlap in the people working on both of those projects. Maybe they have the same technology under the hood as well? |
Another pre-print publishing platform: Quieos |
Elsevier Enhanced Reader is not bad actually. Not as sophisticated as what we're trying here, but already works across all Elsevier journals as long as you have a subscription. |
Qeios doesn't seem to have any relevant features as far as I can tell? It's just a standard article? |
And Substance is just a closed source subcription-model editor that isn't even complete? Again, not sure we can learn much there. |
In principle I like the graph view of obsidian, but not sure how helpful it looks in practice. Seems rather messy. I suspect most users will just switch it off. |
Graph views are really hard to get right in my opinion. |
Yeah Qeios looks like it's a regular paper, but it allows you to paste in the contents of a Word doc which means there is some sort of parsing going on behind the scenes. According to the eLife Lens README, the Substance team is helping with the technical execution. In the I agree about Obsidian, visualizing a full graph is impractical and feels like a gimmick. But navigating through a graph feels natural and intuitive, so I think there's a parallel between navigating the graph of notes you're writing, and navigating the graph of research papers you're exploring. |
The text was updated successfully, but these errors were encountered: