Thanks! Installation instructions are on the homepage indeed

Quarkdown uses actual functions that return values, they aren't macros. As for source readability, it's possible to define functions in a separate .qd file and import it via .include {myfile.qd}

I'd rather say Quarkdown is to Markdown what React is to HTML.

what do you suggest?

The wiki explains Quarkdown’s concept of subdocuments. A subdocument gets created when linking to another Quarkdown/Markdown file and populates a graph. Subdocuments inherit the linker’s properties but are then independent sandboxes that get compiled independently.

A cross-subdocument cross-reference is such a niche use case that I don’t feel like it should break this design choice.

That’s truly one of the best compliments I’ve ever received along my dev journey. Thank you.

I was just reflecting on what I saw/thought! But sure, take it as a compliment, the website and branding are amazing, I'm (positively) jealous of how good they reflect on the product, congrats.

I posted it on my X, hope you don’t mind!

That’s exactly why I built Quarkdown. Flat learning curve for basic formatting, powerful customizations for the rest. Spot on!

I think that's an interesting idea, but you hit the landing page and there's loads of syntax thrown in your face and you're like, man, I need to learn a lot.

But I think this kind of brings up another problem, which is that you can choose not to use stuff if you're writing, but if you're reading other people's docs or editing them, then you need to know all the syntax they use. Most OSS projects with markdown docs today, anyone can open an MR to improve them.

I'll take that as a compliment

No problem!

Easier to read, easier to write. On top of that, Quarkdown runs compile-time logic and scripting.

Thanks! Dynamic animations are from GSAP

What’s GSAP?

Frontend animation library