Web-based Org viewer that is perhaps a seedling for a collaboration tool (Confluence/Notion-alt) that allows plaintext geeks (like myself) to operate in their preferred mode while allowing the non-plaintext-ers to still collaborate in a nice way.

I’m interested… would like to see more. Always looking to find ways to share my eMacs stuff to others who don’t know or want eMacs.

What is this, how does it work and is there a link to where we can find out more?

Perhaps orgweb or easyorg

this is awesome! I've been looking for something like this. I want to add my org knowledge-base to my Gatsby site without having to pandoc everything manually to html

The URL in the screenshot is https://proto.formation.tools/ Maybe that has more information.

Yup -- here is more info: [https://proto.formation.tools/](https://proto.formation.tools/) [https://gitlab.com/formation.tools/eng/proto-01](https://gitlab.com/formation.tools/eng/proto-01) [https://github.com/rasendubi/uniorg](https://github.com/rasendubi/uniorg) Cheers!

Love the idea! Especially if it were easy to self-host and I could share individual files.

Thanks for sharing those links u/deerpig. 🙏🏿 This is indeed the scrappiest prototype we could come up with but we do want to have an option that is self-hostable and managed (that we can offer to startups who don't want to bother self-hosting). Furthermore, we want it to just show the git repos you select to share and for this, we'll start of integrating with Gitlab and then GitHub. I'm also meeting with the author of ProseMirror and CodeMiror (both are famous WYSIWYG editors) to spar on how I can best implement collaborative editing. Currently leaning towards using Replicache to facilitate collaboration sessions and then we may experiment with 1) small git commits upon block level edits (so after changing a heading and leaving it), 2) commit at end of collab-session, 3) commit upon explicit save or 4) auto commit on some interval TBD. Perhaps may become a combo of each and we may settle for creating MRs that one can approve in-app and perhaps squash merge. Problem is that the junior engineering and exec assistance folks at work don't know Emacs but I'd love to collab with them in a format that friendlier (as opposed to the Confluence/Jira, Notion, et al. offering that is out there). I'm getting a stronger response here on Reddit than on HN, so I clearly didn't post it well on HN or my audience is more here (let's say, if it was up to the HN reception, I would have to consider this idea invalidated but looking at the input here, I may have to consider how I can move it forward anyways). 🤔 Interesting learning thus far and thanks for engaging, folks.

Thanks for helping share the link u/Bodertz 🙏🏿, I'll pay attention to place them more prominently next time I publish some work for feedback.

Your primary need would be publishing pages on your Gatsby site you mentioned so would expect to statically build all pages or would it be fine too have a drop-in page that live renders the Org stuff? Just asking because this is a Next.js project and I can imagine easily pointing this towards a raw Org file but embedding it into your Gatsby build pipeline would likely require some undusting of old Gatsby experience (probably my Gatsby stint from 4 years ago is irrelevant now as I'm anticipating that much had changed). So you wouldn't need anything like collaborative editing and you'd rather want this as a package that you could add as a dep to your site? Is that a decent parsing of your situation?

Would sharing repos be a decent level of granularity or would you need finer gained access control as in individual files in a repo only? I was flirting with the idea of allowing folks to mark individual files or sections of files in a private repo as sharable under a unique generated slug/link.

Thanks for the input. The sharing is mostly unidirectional or do you have a use case for collaboration as well? On my end, I share the "sharing" pain, but the bigger pain is that the options for collaboration are so far removed from practical for non-Emacs users that thought changing that UX would at least be a worthwhile experiment. Perhaps my use case is very rare though. 🤷🏿‍♂️ Hence me asking. Do you see yourself and peers/colleagues/fellows using something Notion-like within some of the organizations you're active in? Or is the collaboration tooling sufficiently painless as-is?

You can use [ox-publish](https://orgmode.org/worg/org-tutorials/org-publish-html-tutorial.html) to trivially public org to html

For now, just a scrappy Org file reader. But it's just a set up. The punchline would come with collaborative editing capability (like any collab tool out there these days, think Google Docs, Notion, Confluence, HedgeDoc) with the difference that it makes changes through git commits such that you can time travel back to see a previous state (or see the diff on a time range in multiple views, Kanban, Calendar, Prose, etc.). 💡 Additionally, I would like to conduct NER automatically on the text to extract entities and link them to create knowledge graphs automatically without all the manual linking. Another cool experiment would be to offer some GPT-3 powered paraphrasing option where we could extract three bullet points on a longer text or paraphrase a long section of text for a different audience (kinda like ELI5 or ElI{in marketing, not engineering}). On the lower-tech front, offering great integrations to basically manage your tasks or comment on documents directly from your chat tool of choice (Slack, Mattermost, Rocket, etc.) would be another feature that I would love to have. Currently threads on Slack are painfully confusing (to me) and I want to be able to associate all convos on the chat platforms to the related doc and find them backlinked in said doc. Everything past the 💡 could be features that require us to roll some services that cover this functionality, but the base shell with the presentation/rendering and collaborative editing capabilities (sans the backend which anyone deploying can choose to be Yjs, Liveblocks, Replicache or whatever else you want to roll) would remain GPL3. The all-batteries-included setup could a managed offering but this is too early to say.

>Web-based Org viewer that is perhaps a seedling for a collaboration tool (Confluence/Notion-alt) that allows plaintext geeks (like myself) to operate in their preferred mode while allowing the non-plaintext-ers to still collaborate in a nice way. Indeed. I export my files to HTML quite a bit. Where I'd like to go next is having my git repos automatically readable to my colleages in a manner that is less painful to grok than the current Gitlab/GitHub presentations of these files. Eventually, I want to be able to use this like HedgeDoc e.g.: collaborate during a call in such a file together and the auto-commit once we're done or something like that.

> Where I'd like to go next is having my git repos automatically readable to my colleages in a manner that is less painful to grok than the current Gitlab/GitHub presentations of these files. what about Github Workflows? There are several emacs-based CI solutions, so I think it's possible to publish orgs automatically.

That would works for the export path. It doesn't quite help us solve the problem of junior devs and administrative folks on the team wanting to make changes or collab. They expect something more Notion-like (at the very least the admin folks should not first have to learn git) which is why we tend to naturally revert back to Notion, Confluence/Jira, Asana, Google Docs or any of the more user friendly alternatives for non-devs out there.

I really like the idea of mixing a todo with a Notion-like experience. You're offering a great alternative to Notion's database feature (which I love). In terms of collaboration I see you've considered Liveblocks. You could show who's present at the same time, sync changes, support conflict resolutions and implement undo/redo. They have a few examples/guides: Collaborative Block Text Editor example: [https://liveblocks.io/examples/block-text-editor-advanced/nextjs](https://liveblocks.io/examples/block-text-editor-advanced/nextjs) Undo/redo guide: [https://liveblocks.io/blog/how-to-build-undo-redo-in-a-multiplayer-environment](https://liveblocks.io/blog/how-to-build-undo-redo-in-a-multiplayer-environment) ​ Something missing so far is an example of a JIRA-like product, where you could see who's in a task/story, or even in an epic/group right now, and have the content updated in realtime. That's something you could do with your tool that'd be very cool.

Mostly I like to have ways of exporting in attractive formats to embed in the tools my company uses: MS Teams, Confluence, Sharepoint, Outlook… etc. But I usually end up copy and pasting and formatting with the target tool. Yuck.

Are you aware of logseq? Not 100% true to org syntax, but I can use it pretty well on mobile with my org-roam notes. They are going to offer sync and real-time collaboration soon.

Am aware of LoqSeq and am really looking forward to their sync and collaboration offering. 🥳 Used it for a while (as I did Obsidian) and then weirdly pivoted out because using different clients for text editing became a pain for me. That's how I landed on Emacs again (perhaps like 10mo ago) where I now have my notes, emails and source pretty accessible within the same-ish toolbox with great linking capability. In my team, I need something that doesn't quite require folks to install a client so we needed something that is just, hate to say it, more Notion-like in terms of usability (just log in and view/edit text without having to put much thought into the tools or underlying document format). Ideally, we'd have a way of allowing folks who prefer the browser to stay in there, allow some to stay in VSCode and allow others to stay in Emacs and still collaborate seemlessly -- that reality, however; is just a naive dream of mine. 😅 LogSeq was visually a bit busier with the roam-like presentation which is perfect for more technical audiences but didn't quite land with some of the non-devs users who we want to grant easy read and edit capability as well.

For folks still watching this, it should now be possible to point this thing towards any openly accessible raw Org content on the web. I'm hoping that seeing your own files through this (slightly foggy) lens, helps trigger the imagination of where this is going. Collaborative editing capability and git integration are next on the list. Meanwhile we keep working on uncluttering and unwrecking whatever we call our UI atm 😅 Thanks for all the input. I'll be tweeting about the project's progress on Twitter under the handle vidbina for y'all to follow this journey and I'll be hawk-eying the comments here for any input.

adding that to my list of things to check out! thanks man!