What a lot of Scratchers have been trying to do is create a good guide that can help scratchers. Sometimes those guides get sticked, and sometimes not. Here I will tell you how to write a good speech that might become sticked.
Table of Contents
1. The Title
2. What to write about
3. Make sure
4. Don't leave your audience hanging
The title
The main part of your thread is the title. You have to make sure your title is good and not too long.
To make your title good is easy, make something that people will want to read. One of the worst title for a guide is this one:
This is a Guide for Scratch
Okay, well what kind of guide, we want to know. Keep your title broad, but also specific. This is a good title:
How to make a good Scratch project
-------------
To make your title not too long is too lower it down, step by step. For example, I will break this title down for you.
This scratcher wants to create a guide about panther, BYOB, and art programs. They put this as there title:
An easy, simple guide on how to use panther, BYOB, and art programs!!
First lets take out any unneeded words. Now this is the title:
A guide on how to use Panther, BYOB, and art programs!!
It already looks smaller. But it still seems to long, so lets take out the "A guide on" part. It is not really needed. So, so far this is the title:
How to use Panther, BYOB, and art programs!!
There, now look at your title, simple short and I would want to read that.
What the audience thinks of this:
Write down below any additional facts you might want to add to this section
_____________________________________________________________________________________
What to write about
Some people get stumped about what to write about. Well, think of something you do good in scratch, something that a lot of scratchers might not understand. Or, write an FAQ about something. But, what some scratchers try to do is make a guide on how to become famous in scratch. I would recommend not to do this. This only encourages people to spam to get there projects famous.
Or you could write a guide on how to use BBCode in scratch (though I wouldn't do that). One broad thing people try to do is teach people how to use scratch. You could do this, but there are already so many guides on how to do scratch.
Or you could be like a class. Have a lesson everyday (by editing your topic) on stuff about scratch. That would be very interesting.
What the audience thinks of this:
Write down below any additional facts you might want to add to this section
_____________________________________________________________________________________
Make sure
Okay, so you got your idea down. The most simplest thing to do is search your topic name in the search bar and see if anything pops up. If something pops up, then go back and think of another idea. If you see nothing has popped up, go check the wiki. If you are a wiki editing user do this:
Go to the wiki, type in the search bar what the name of your guide is called. Then if anything pops up, go to that and read it. See if you can edit it at all. Then go back to step two, and think of another idea. If nothing pops up, move on to the next step.
If you are not a wiki editing user, do this:
Go to the wiki, type in the search bar the name of your guide. If something pops up, look at it, read it. If you think something is very broad or it doesn't give much information, go ahead and make your guide with more detail.
If you think the wiki has a good sentance, then write this in your guide:
This is what the wiki wrote:
Put text here
What the audience thinks of this:
Write down below any additional facts you might want to add to this section
_____________________________________________________________________________________
Don't leave your audience hanging
Some guides have good topic, but some information in them are very broad or missing. If you really need some help on your topic because you don't know much about it, then go to the real wikipedia, type in the thing that you are having trouble with. And I am sure something is going to pop up.
What the audience thinks of this:
Write down below any additional facts you might want to add to this section
_____________________________________________________________________________________
Offline
I cud writez a gud guide.
I'll hav an advantge becuz I can speell and grammer good.
Offline
Bump, I guess
Offline
BellijerintToast wrote:
I cud writez a gud guide.
I'll hav an advantge becuz I can speell and grammer good.
do you mean: "I could create a marvellous guide. I can showcase my superb range of spelling accuracy and effective grammar."
Sorry, but your spellings and grammar are not good. But I am sure you'd be better writing in your own language- presuming you're not a native.
Last edited by Borrego6165 (2012-04-02 03:02:18)
Offline
Borrego6165 wrote:
BellijerintToast wrote:
I cud writez a gud guide.
I'll hav an advantge becuz I can speell and grammer good.do you mean: "I could create a marvellous guide. I can showcase my superb range of spelling accuracy and effective grammar."
Sorry, but your spellings and grammar are not good. But I am sure you'd be better writing in your own language- presuming you're not a native.
You know s/he's a troll, right?
Anyway good guide and stuff
Offline
bump
Offline
This is fairly accurate, & is mostly what I consider when making Walls of Text. I'm glad to see that this guide has been made!
Offline