What's the best way to contribute back to Zettlr?

First, thank you for this initiative. I highly appreciate it. Then, I think the biggest help indeed is fixing bugs! Feel free to tag me on github in case of any questions.

A good contribution to zettlr could be to provide example files, a whole example workspace.

I am since days reading about zettlr but don't get started. That's because an abstract manual to me is pointless. It's like unsuccessfully reading linux man pages. When I would need them I ask google for examples, and if I find one or more I start there and try out how to adapt them for my needs. Completly unthinkable to solve any problem by reading man pages.

From reading the zettlr doc I may get an impression what an internal link it, but I would not know what the actual use of it is. I need examples, examples, examples, and guess what? More examples.

So if you could accept that helping a new user with an example - which from the beginning is meant to be of use for many users to come - is helping zettlr, then you have an idea of what you could do ;-)

Lets say you provide some example files for a work called "cultivation of tomatoes on mars", you invent some zotero bibliographie, some zotero citations, annotations, notes, and some initial zettlr files, ideas (Mark Withney from the Marsianer as the first farmer, references to first experiments on the moon, what ever)

Then you show how all those ideas, citation, notes are linked, grouped, back and fourth and how this grows to an actual work in zettlr ... with links, tags, references and what not

No, I don't grow tomatos, nor do I have any affilation to the space, and I am not writing a new mobie script.

Anyone?

michaa7 The tutorial does some of that. It should come with your first installation, but it's here also. It could be extended somewhat with more links and examples, but most of the concepts are demonstrated IMO. I think it should actually not be too elaborate and specific, because the beauty of zettlr is that you can organize your notes in any way you want, so IMO the tutorial should not prescribe the one way to do it.

gbm

IMO the tutorial should not prescribe the one way to do it.

I 100% agree ... with one important constraint: yes, there may be people who will see it as "the one way", but there are others who need it not as "the way" but as "a way", "as one practical example" on how it could be used. And yeah, three completly different examples would even be better.

:-)