wow, went down a solid rabbithole with that one. Very interesting stuff - looks like a good area to contribute to!

I Love Codex, the conversations tangent so beautifully. i think at one point we were talking about Sand worms and the Fremen in Frank Herbert's Dune and then talking about the entity relations and attributes of the editor. Wonderful developer

oh yay! i got a role 😄 unexpected

i've been a bit slow to merge pull request on the docs. just did a whole batch yesterday so a bunch of new Taxonomists 😅

im a little scattered, but im still trying to get through all the docs as a learner, i'll fix what i can when i see it 😅

that makes two of us 🙂

yeah scatterbrain, to help with it I wanted to use a Pkm, what do I do instead contribute to developing it and forget to use it xD

Neat!

Click-bait-y title 🙂 Not everyone would click the title "Wiki inventor creates federated wiki" 😜

Haha

Just a heads up, @User got his second dose of the covid vaccine... so today has been a recovering day for him. He should be back on his feet in no time (and by feet I mean back on the computer 🙂 )

I saw around here dendron has taken a look at org-mode as a possible implementation. Have you guys checked Asciidoc? I mean, I love org-mode but asciidoc makes more sense to me for an application like dendron. Has some beatuful features for customization (like attributes in your document) and exports documents in a very profesional way. We use it to write pdf client reports and whitepapers. And I think with ascidoctorjs (https://github.com/asciidoctor/asciidoctor.js/) could be great since has a great API for extending the syntax or parsing features

I am with you. I loved Markdown and got a lot of people to use it. However as much as it is quick and easy to use, when you need more advanced features you really start to realise it was not thought out properly. That is when I discovered AsciiDoc. It is a lot better in so many ways. I wish it was more popular. Funnily enough, I discovered Dendron while looking for an AsciiDoc extension in the VSCode marketplace. When I found Dendron, I searched around the Discord channels and found that Kevin likes AsciiDoc. I wanted to see how complicated it would be to get Dendron to "manage" AsciiDoc files. Unfortunately it is not trivial. The best I could come up with, is the fact that Dendron uses "remark" for processing markdown files, which also has a lot of good plugins. With the following plugins, remark-directive and remark-sectionize, I can get most of the features I need (which come by default in AsciiDoc). Here is the issue I created: https://github.com/dendronhq/dendron/issues/507

Great to see the 0.31 update, gonna play more with pods

@User @User i'm personally a fan of asciidoc - the decision to use markdown was for accessibility to a greater audience. that being said, dendron markdown is already a superset of markdown since we custom syntax that will probably borrow some elements from asciidoc moving forward we'll also have pods to allow for the conversion between dendron markdown, markdown and ascii doc

summary generated using https://tldrthis.com/

It was the same for me. I discovered Dendron looking for a good Asciidoc alternative for PKM 😆 . Is sad that asciidoc is not more popular, actually there are no reasons since asciidoc is amazing and understands Markdown syntax, so the transitions is less painful. And the guys from asciidoctor are doing a great job. Actually not long ago I was thinking on building my own PKM app on top of asciidoc but I didn't had the time. The most weird part was thinking on how to implement cross-document links since asciidoc approach is different. Thanks for the link to the issue! I will take a look

didn't hear Asciidoc before, how is it better (superior) than markdown?

Yes, I understand that sometimes it's not about choosing the best option but the more known and widespread. That was one of the reasons I left org-mode, because you had to expend a lot of time in configuration to just for example create a "bloggable" document

I guess it depends in the context too. Asciidoc was initially created for technical documentation. But now is actually a great tool for writing: it can create really professional PDFs, epub, or dockbook from just the plain text. Actually its html render is great too. Take a look at it if you are interested. It is the tool we use in Confluent for write deliverable whitepapers, books and reports

I've use latex for that before, going through some vids and documentation. Thanks for mentioning it, I wouldn't know it if you guys didn't mention it

Yeah, actually avoiding the painful latex is the reason we use adoc haha

Same. I wonder if adoc has more of an appeal for people who used LaTeX

> how is it better (superior) than markdown? In nearly every way. It has been thought out properly from the start. If you want to do something a little bit advanced it has an elegant solution. Here is just a list off the top of my head: - Precise image placement - Document pre-processor (similar to YAML but more powerful) - Table of Content - Great bibliography support and footnotes - Embeds backed in - Good referencing syntax - Admonition sections - Precise image placement - Proper syntax for quoting people - Add containers easily to each section - Plugins to generate nice semantic HTML (very easy to theme with CSS) - You can use it to write a book - Did I mention precise image placement? A quick intro is here: https://asciidoctor.org/docs/what-is-asciidoc/ More detailed guide here: https://asciidoctor.org/docs/asciidoc-writers-guide/ Both pages are written in normal AsciiDoc (i.e. no extra plugins are used. It is what you get out of the box) and use the "default" HTML output.

wow

I read through the asciidoc-writers-guide, turns out it is amazing

you can do MANY things with asciidoc

Yes and it all comes straight out of the box.