but also by other people with lots of experience and who know all the tricks.
I’d think that adding little tips and tricks through the getting started guide (for example the auto repeat and increment for adding labels while depressing [Ins] helps a lot with helping newbies who read it up to speed with KiCad and how to use it effectively. Anyone who knows such tips can add them. It is of course always some sort of balance.
So my new PC is up and running now.
I made a fresh fork of the KiCad documentation on gitlab, cloned it my own PC.
I also got some help from a friend who helped me with ironing out some GIT issues (and I only gave him half a beer)
I also made a trivial (but real) merge request to test my workflow:
@craftyjon Have you made that group DM yet? Where can I find it?
I do not understand this:
The PNG picture with the workflow flowchart is a bit troublesome, but most of the guide can be updated relatively easy. After I’ve managed to get to a merge request 2 days ago, I’m now ready to do some more serious work.
@gkeeth How are your efforts going? A simple way to coordinate and prevent doing double work is to agree who does which chapters. After most of the chapter are updated collaboration gets more complex, but git should be able to help there.
@Aris_Kimi You’ve also shown some interest to help, and may want to join the group DM that craftyjon promised. Apparently @ixhuti has also shown interest to work on the Blue/Green/Red flowchart.
At the moment I’m mostly waiting for some global coordination of who does what, as apparently there is now some interest from several people to work on this.
As a bystander who wishes he had more time to donate to this effort, I’m happy to see a group effort working on this. I look forward to seeing the end result.
A big thank you to all who are able and willing to put in this effort.