At least a start:
http://ssalewski.de/nimprogramming.html
http://ssalewski.de/gtkprogramming.html
And of course
You could try running through https://narimiran.github.io/nim-basics/ or @Stefan_Salweski Nim Programming book. And then with that knowledge go through Nim Days: https://xmonader.github.io/nimdays/
This should give a beginner a stable foundation and enough projects to build and tinker with. There is currently no resource that I know of that combines both for beginners, they are very hard and time consuming to make :(.
Very beginner friendly tutorials:
Hope this helps, and good luck on your journey. Before you know it you'll be an absolute killer.
The ones on https://nim-lang.org/learn.html are not like "python crash course".
What specifically do you miss from Python Crash Course? That book has an introduction where you install Python, and then a Part 1 that is a tutorial that shows off language features with examples, and then a Part 2 that walks you through three projects: a game (using pygame), dataviz (using mplotlib, csv, requests), and a web app (using django).
So, how to install Nim: https://nim-lang.org/install.html , a tutorial with examples: https://nim-lang.org/docs/tut1.html , and specific projects you can find in various places; Nim in Action has a networking and a webdev demo.
Part 2 that walks you through three projects
My personal feeling is that larger example projects in a book make not so much sense. Example projects are great when they cover exactly the topic which the user is interested in. But relative useless otherwise. Dom's book had same fine larger examples, but unfortunately none of them was from my area of interest. Or GUI: We have currently at least 20 different GUIs for Nim. So when there is one great GUI example in a book but you want to use a different one? Or graphics? Great 2D example when you are interested in only 3D? Great Godot example when you want to use SDL2?
What we really would need is a set of a few dozen really good explained medium size example projects. We have at least some people like Mr Felsing (maybe retired) or Mr. Ratsimbazafy who can create and explain examples well. One nice blog post I remember was
https://hookrace.net/blog/writing-a-2d-platform-game-in-nim-with-sdl2/
But for such nice example projects the authors should get at least a few thousand dollar compensation for their efforts of course. And that is the problem for a small community.
Example projects are great when they cover exactly the topic which the user is interested in. But relative useless otherwise.
I don't agree, full programs can be copied and edited. It's much easier to delete sections that you don't need rather than searching for one example that shows how buttons should be used and then there is a different example for textviews and another for menus. There is a reason the "Todo App" is the standard example.
Great Godot example when you want to use SDL2?
So that's why you shouldn't have a Godot example in a book? Seriously, that's the definition of a straw man. "X doesn't help when you want Y, so let's not have X".
But for such nice example projects the authors should get at least a few thousand dollar compensation for their efforts of course. And that is the problem for a small community.
Er, why should people who passionately write about their favorite topics get compensation at all. And what does it have to do with community size. You act like if only you wrote your Nim book about Rust/Go instead you would see donations of a few thousand dollars. Feel free to try.
I don't agree,
Why do I know your name just by reading these three words?
full programs can be copied and edited.
For simple people like me it is simpler to start with one of the books of Wirth or the Dragon-Book as to copy parts from your compiler. Or when I wrote my tiny Ned editor I tried to start with gedit sources. Gedit is called a basic editor, but already 100k lines of C code. I was not smart enough to understand it. Or the Constrained Delaunay Triangulation, a really hard target for my simple mind. There are some implementations at github available. Most 10k lines of OPP code. OK there was one in C, not that bloated, where I was able to understand at least parts. But finally I started direct from the published papers again.
So that's why you shouldn't have a Godot example in a book?
I would not buy or at least not read a book with a Godot example when I am not interested in writing a Godot game myself.
get payed several thousands of dollars for writing their blogs.
I would not really assume that someone creates a well explained blog example, which may be 100 hours of work, for free. Decades ago people published such stuff in computer magazins and and got paid for it.
Or when I wrote my tiny Ned editor I tried to start with gedit sources. Gedit is called a basic editor, but already 100k lines of C code.
Yeah, but that's C, Nim is not C.