well, but you can still ask, the writer can be reached via the forum.
That is true. But then, what if the writer is inactive for a certain period of time? Perhaps he doesn't even make a return. That's when you won't be able to know what they truly meant when you attempt to ask them.
I can't base it off their history, anyone can post tutorials. Teaching others is again, the best way to learn. However, if the tutorial is not really understandable I will not make any rules against it but advise them of changes they could make to improve their tutorial. Saying coders who are intermediate or advanced should be the only ones who can make tutorials can sound pretty unwelcoming.
Even if the information or explanation is not fully understood, this is the opportunity to improve, get feedback and have information correction. Again, it furthers your learning with that particular topic.
When I said to base it off their history, I was referring to you going about asking a few people to post tutorials - Not basing the tutorials off of everyone's history.
Regarding only being of "intermediate" or "advanced" levels to post tutorials, was not meant to be taken out of the context I intended it to be in. I was meant to say that being of those levels is when it's best to post tutorials - I didn't mean to say that beginners shouldn't until they've made progress on their education. Beginners can be free to post tutorials, but being of intermediate or advanced levels are in my opinion, again, the best levels to post tutorials at.
Going back to the poor English discussion, I think what people should do is go about online or ask their teacher(
If they're in school), about the quality of their English. If others online or the teacher provide more criticism than compliments, that should be taken as a sign to further improve. I believe one tip that could be offered is to write mock-up tutorials and have them sent to a CF staff-member for review on the quality. Not only does this benefit the writer and their English, it also helps improve their writing-skills in general, and also gives them a chance to work on explaining things in more detail.
I believe you misunderstood what I said, what I mean is that are these scripts/resources being published by CF and or encourage members to publish scripts/resources.
Well, if we're going with the userbase, then either users can submit scripts to be uploaded to a repository or have them submitted to the Resources section of the site. So, they still are technically being published by CF.
If we're going with CF writing and publishing themselves without getting the userbase involved too much, then perhaps staff-members will write the scripts and whoever has access to the GitHub, uploads them there to a repository or again, in the Resources section.
Any sized project can be listed - Small to huge. I'm considering all sized projects. E.g. a script that adds an A in the name of every file on your computer to Advanced calculators.
In my opinion, the scaling of projects should be based off of CF's current size. When we start making projects, we of course, start small. There won't be much to do, but everyone can get involved, and plus, there will be less headaches too. Then as the site grows in size, we scale to bigger and better projects. Ones that will require more users with a good amount of experience to be involved - Of course, beginners can contribute to these larger projects too, to help gain experience. The only issue they'll have as a beginner is trying to understand what more complicated parts of the code do.
As you said, start off with simple projects that don't require much involvement but can still interest people, like writing small, automation scripts. Once you start to scale larger, you move onto as you said, an advanced calculator, an RPG game, a chatbot, you get the idea.
You definitely do not want to start extremely big and ambitious projects with such a small userbase which contains more beginners than experienced people. That will lead to little development and involvement happening, with most involvement probably being:
"Looks interesting. Keep it up!" and feature-suggestions, while the experienced work their butts off 5+ hours a day.