csarven on main
Hey @dgarijo . Generally yes and it'd be no different than dokieli's CSS and JS being included in any HTML. There are of course some markup patterns that dokieli has in which you can get more out of the tool - what it can detect / display. The pattern is fairly straight forward to follow / generate IMO.
dokieli doesn't offer a transformation from anything to dokieli HTML. That's out of scope. So, you might want to find a tool that gives you a simple HTML. From what I've seen - and I can't say I have much experience with it - pandoc is pretty decent to get things going. You'll really have to massage whatever it generates if you really want to bring it closer to HTML like in articles listed in https://github.com/linkeddata/dokieli/wiki#examples-in-the-wild -- but don't take that as absolutes. Just in the right direction of things working properly.
See https://dokie.li/new as what the outer HTML should look like. Aside: see how the HTML patterns in https://dokie.li/ or https://dokie.li/acm-sigproc-sp or https://dokie.li/lncs-splnproc or https://csarven.ca/linked-research-decentralised-web .. essentially have no difference. It is just the CSS doing the work.
My suggestion is to take it step at a time. Unlikely that you'll get a perfect document coming out of LaTeX... but dig around for XSL-based approaches as well.
ld.store.serializers['text/turtle'].serialize(g._graph)where the return contains the accumulated prefixes. Not sure if there is something I can do before that (eg. some option to SimpleRDF.parse?) or as I call that.