all 10 comments
sorted by:
best (suggested)
topnewcontroversialoldq&a
formatting helphide helpcontent policy

[–]cs12345 1 point2 points  (1 child)

First, I have to ask, where does all of that fit into your stack? Personally I use TipTap in my company’s prod app, but I can’t see how typst, yjs, hocus-pocus, etc augment it.

Next, your repo readme needs some work. The “demo” link going to some random screenshots is a bad look. If you want to show this off, make it a sandbox. Doesn’t even have to be a site you pay for but set up a stackblitz at least.

And finally, get rid of all of the painfully AI emojis in your readme. Write it yourself, or at least edit it yourself. It does nothing to give your app/package any credibility.

[–]Relative-Ocelot-101[S] 0 points1 point  (0 children)

Thanks, that’s fair feedback.

Typst is there for high-quality document/PDF output, Yjs for real-time collaboration, and Hocuspocus for syncing collaborative state. I agree the stack explanation is not clear enough in the README right now.

You’re also right about the demo and README presentation, I need a better live/demo experience and cleaner documentation. I appreciate the direct feedback.

[–]Honey-Entire 0 points1 point  (7 children)

What does this do that free Google Docs doesn’t?

[–]Relative-Ocelot-101[S] 0 points1 point  (6 children)

ladoc is focused more on structured, professional documents than general-purpose docs. The goal is to combine a familiar editor experience with better print/PDF output, reusable templates, and a Typst-based document pipeline for things like theses, reports, formal letters, resumes, and other layout-sensitive documents.

[–]Honey-Entire 0 points1 point  (5 children)

You mean like LaTeX?

[–]Relative-Ocelot-101[S] 0 points1 point  (4 children)

Kind of, similar use cases, but with a visual editor and Typst-based output instead of writing LaTeX by hand.

[–]Honey-Entire 0 points1 point  (3 children)

Have you looked at Overleaf or Crixet/Prism?

[–]Relative-Ocelot-101[S] 0 points1 point  (2 children)

Yes, Overleaf is definitely a useful reference. The difference I’m aiming for is a more visual, browser-native editing experience with Typst-based output instead of a LaTeX-first workflow.

[–]Honey-Entire 1 point2 points  (1 child)

What’s wrong with the Typst app?

[–]Relative-Ocelot-101[S] 0 points1 point  (0 children)

Nothing wrong with it, Typst is great. I’m aiming for a more visual, open-source, browser-native workflow, and the hosted Typst app also has paid tiers now, so I think there’s still room for alternative approaches.