Contributing - Docs updates

After seeing the 1.0.0 release yesterday and applying it, I learned of the existence of the desktop client and went to give it a testdrive. I ran into some difficulty setting it up. There were clues in the docs and in the release announcement, but ultimately I needed to troubleshoot with Claude to surmount the obstacle.

Having succeeded, I’m motivated to pitch in by drafting a documentation update to ease the process for the next person. This is something I’d be interested in contributing for a variety of issues I’ve tackled while adopting (and loving) vikunja.

In the interest of minimizing how much work my contribution would create for the devs/maintainers, I went looking in github for a docs repository that I could target with a PR, but I didn’t see one. I’m pretty new at collaborating with github tho, so it could be my ignorance.

What would be the best way for me to not only suggest doc updates, but to actually do some of the doc drafting/development in a frictionless way for your team to adopt or comment on?

Thanks!

@kolaente

Thanks for wanting to contribute!

The docs are here in the website repo: GitHub - go-vikunja/website: Official Vikunja Homepage

To use the desktop app, it’s probably best if you create a new page at src/content/docs/usage - just look at one of the other pages in that directory for how to set up the metadata etc.