(Auto)-sync content directly from Roam

[Stvad]

I think it can be a great experience to just have a Publish button inside Roam (based on [[roam/js]]) as an entry point.
When user presses this button - the roam/js client would filter things according to your configuration and send them to the [[API]] that would do the publishing.

It can also run on a regular basis for automatic publishing (as long as you have Roam tab open)

Roadmap: https://github.com/roam-garden/i/projects/1#card-56652560

Configuration

Option 1 (preferred): Store configuration in a special page inside Roam. I know of several

Option 2: Have configuration stored inside the roam/js snippet people would copy

Filtering

I'd like to re-use the logic from https://github.com/roam-garden/roam-export to provide unified experience for "upload json" and "publish from Roam" use-cases. That package operates on Roam JSON export though. So a first step before I can reuse it is to generate a JSON-export like data-structure myself.

[[David Vargas]] is doing something similar in dvargas92495/generate-roam-site@df634c8

Other interesting resource on that https://davidbieber.com/snippets/2020-12-22-datalog-queries-for-roam-research/

Other possible features

• This may also enable extracting information that is not currently encoded in JSON export (Roam "Document“ style missing #19)
• Make the "make-public" marker subtly change the background of the page inside Roam (or add some other indicator). To make it obvious that the page you're editing is shared.

Roam Extension name options

• Arborist
• Plantsman
• Gardner (conflicts with internal things)

---

[kalmir]

That would indeed be great.

[Stvad]

you should upvote it then ;)

[Stvad]

Upon initial research I figured out a way to do this in an easier then expected way! I hope to have a first test version by the end of the week! LMK if you want to be an early tester!

[JayFarei]

hi @Stvad - can I confirm this approach creates a filtered export locally before sending it to roam.garden's APIs?

Is there a way to add a verification of the export in the middle to reassure the user that no information is leaked?

I am experimenting with it right now and I much prefer this method than the full export & server side filtering, however I am a still a bit anxious of potential data leakage as the public content lives alongside private content in my graph.

[Stvad]

Hey @JayFarei! Yes that is correct all the filtering happens locally 🙂 I note on that in the FAQ section ;)
And the plugin code is open-source at https://github.com/roam-garden/plantsman

Also, the upload process on https://roam.garden/ was updated to also do filtering locally, so now only the data explicitly marked public makes it to the API regardless of the upload method

Is there a way to add a verification of the export in the middle to reassure the user that no information is leaked?

There is nothing like that atm. Can you elaborate on how you see this interaction working?

I am experimenting with it right now and I much prefer this method than the full export & server side filtering, however I am a still a bit anxious of potential data leakage as the public content lives alongside private content in my graph.

Makes sense, can you elaborate on what kind of things would you find reassuring for this? :)

[JayFarei]

Not sure exactly how to do that - Obsidian publish I think offers a UI that shows which pages will be published I believe.
You could implement a similar step in your Roam/js publication workflow so that a user can spot mistakes prior publication.

Alternatively you could also offer the option to save on the local machine the exported markdowns (I imagine you do that server side atm for the gatsby template?) & a way to keep those in sync with your gatsby site agent? (that makes your service also somewhat Roam agnostic => e.g. logseq)

[Stvad]

Not sure exactly how to do that - Obsidian publish I think offers a UI that shows which pages will be published I believe.

Hmm, it can be a lot of pages though 🤔. Would be interested to see how it looks in Obsidian publish.
Will experiment with doing something like that, should probably create a separate request for it though

Alternatively you could also offer the option to save on the local machine the exported markdowns (I imagine you do that server side atm for the gatsby template?) & a way to keep those in sync with your gatsby site agent? (that makes your service also somewhat Roam agnostic => e.g. logseq)

Not quite sure this addresses the issue in question 🙂. And yes this happens on the backend, though what's generated is not markdown, but MDX using & custom components. + There is a lot of post-processing done on generated code, so it by itself is not very useful =\

[Stvad]

started #63 for confirmation dialog discussion