-
-
Notifications
You must be signed in to change notification settings - Fork 106
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
[ENH] Static export of org-roam-ui #294
Comments
It seems hover to preview does not work. I wonder what's causing it. |
Nvm. i just fixed it on my own. checking the logs and all |
HMM @wylited maybe i should assign myself for this. I just found out that I can just use the patches from jgru's fork and add my own. not sure if the dev team here wants to move forward but expect a PR soon. it's a very smol change to be honest with some added new |
@uncomfyhalomacro Do you need testers for the UI export you're working on? |
i havent started yet since i didnt get a go signal from the maintainers. but i am willing to do it after I am done with personal life stuff. it's very trivial to do so tbh because of @jgru's patches |
@uncomfyhalomacro, please do let us know after you work on it and need testers. This would be really useful for me too! |
@wylited May I ask how you've set up the fork? Have you removed |
You could check my repo's readme. I'd love to see this in the main package so that I wouldn't have to deal with selecting the fork. |
in any case, i will start working on this over mid september, probably around sept 15. i will try to keep up with the upstream changes and PR. i feel like the maintainers are kind of inactive though so i hope once i pr, they will review it. |
I can also just open a PR of my branch which should merge just fine. Maybe the maintainers agree to incorporate it in view of the general interest. |
any progress on this? |
Sadly I stopped pondering about it since life just became busier now. I do have a workaround I mentioned here |
Tefkah is most likely busy with life right now. I was hoping to be able to provide more development support on org-roam and org-roam-ui as I'm young, I use org-roam quite a bit, and I'm free enough to work on it. Unfortunately, I just haven't found the right entry vector yet. (on a separate note, maybe mine and @uncomfyhalomacro knowledge bases can be added to prg-roam's md) |
I believe it would be beneficial if statically exporting the ui as a next.js static website was avaiable as an option.
This is currently implemented in jgru's forked branch, however, hasn't been touched in a while and could use some more streamlining improvements to make it easier to use.
I currently have a static export setup, and it is a mild pain to export it each time I update my notes. (view it)
I believe this is beneficial as people would like to share their notes in the amazing website that org-roam-ui provides statically to the whole world, rather than forcing people to manage the org files themselves in a git repo.
Furthermore, I would love to try and implement this myself in my free time, if you don't mind.
The text was updated successfully, but these errors were encountered: