The CNC answer you actually came for

CHIP is a free reference for hobby and prosumer CNC routers. It covers the whole road from "what is a stepover" to "why is my 3D finishing pass leaving vertical lines with a tapered ball nose". No sign up, no course to buy, no video to sit through before you get the answer.

Three ways to use this

Search. The box on the left searches every module, every answer and the glossary. Type what you would say out loud: "burning", "fuzzy edges", "tabs breaking", "bit broke", "circle not round". You do not need the correct technical term, because the modules carry the wrong terms too.
Browse by area. The bar across the top splits everything into ten knowledge areas. Each one lists its modules in the sidebar, roughly in the order a person learns them.
Follow the path. If you are new, the Start Here path is a structured week that takes you from unpacking to a finished first project.

What is in here

The one rule that runs through all of it

Every number in CHIP is labelled with what kind of number it is, because the difference matters more than the value:

Formula A relationship that is always true. Chipload is always feed divided by RPM times flutes.
Rule of thumb Something experienced people find works most of the time. Useful, not exact, and it has exceptions.
Starting point A setting to begin a test with, then adjust based on what the cut tells you.
Spec A published figure from a manufacturer. Check it against your own tool, because it is theirs, not ours.
Measured A number you get by measuring your own machine, which beats all of the above.

CHIP will not give you a single magic feed and speed, because there is not one. Your machine's rigidity, your router or spindle, the exact bit, the flute count, the material, the workholding and the depth of cut all move the answer. What CHIP does instead is explain which way each of those pushes it, so you can reason your way to a setting and know what to change when it goes wrong.

If you only read one thing

Read Chipload. Almost every cutting problem a beginner has, burning, broken bits, fuzzy edges, a router that screams, comes back to chips that are too thin. It is the one idea that makes the rest of the numbers make sense.

Something wrong, or missing?

The Feedback button in the corner sends a note straight to us, and it automatically includes which module you were reading. Wrong setting, broken link, a topic that should exist and does not: all of it is welcome. CHIP grows from what people ask for.