Tutorial Section

[Fucking Moron]

This is just something I've always had a personal problem with this. I don't know about you guys.

But I feel if instead of just saying, do this, this, edit that, this, and these files: and you're done!

It leaves the user puzzled for one as they have no idea what they're actually doing, and they really didn't learn anything. Which is the point of a tutorial, right?

So I feel that their could possibly be a decrease in all these "help" threads in the help section if in the tutorials you talked about what things are, what you're doing, and things of this matter: ofc keeping it relevant to your tutorial.

pls no hate

[Riigged]

I mean, you can just read the code too, most people can care less how it works since most tutorials are one time things they only have to add once and as long as the code is given to them they don't care HOW it works as long AS IT WORKS.

[Lxys]

Not really hard to compare it.

[[MPGH]Ahl]

Isn't that what a tutorial is?

I mean if you don't understand in the first place, ask and learn. Or just self-learn. It isn't hard, many have done this before.

[Fucking Moron]

Isn't that what a tutorial is?

I mean if you don't understand in the first place, ask and learn. Or just self-learn. It isn't hard, many have done this before.

Then why do we have the help section if you can just do what you say?

[Kithio]

Tutorial : noun

Computer - secondary meaning

a manual explaining how to use a particular software package or computer system.

--

A tutorial is made so people can LEARN what the actual instructions they're given are for. If you want to give people code without explaining you shouldn't call it "Tutorial" but a "Snippet"

Snippet is a programming term for a small region of re-usable source code, machine code, or text.

If you're going to call it a tutorial. Tell the users what they're actually working with!