I have no issues with those changes.
But I also don’t think anyone using workspace offsets doesn’t understand min and max on each axes, or really care where or if each axis is labeled. To much information can cloud the subject.
As long as you understand what is going on with workspaces is the most important. Like for me, I will probably add a specific example to solidify how and why one might use this.
As an example. I had to change pictures on board wiring because I get emails about a missing driver. Too much info can cloud the subject.
Some use 4, 5, or 6 drivers. I am not adding pictures for each if I don’t have to. So I choose to edit down the pics. Or show them with no drivers installed to eliminate confusion.
Yep. You make a fork (which copies the repo to your account). It will make a “branch” (a version). You can edit that version, because it is in your account. Then you will make a “pull-request” from your “branch” to the main one. The PR will give us a place to see what changes you’re suggesting and comment on them before approving them.
Once the changes are accepted, the PR is “merged” into the main branch. After that, you can safely delete your fork.
This all sounds weird and arcane (it sort of is). But it does make sense in the larger ecosystem. It just needs a decoder ring to get started.
close older topics to help with spambots, and faster new user questions.