From a post I made in natty's Newsletter survey thread some 10 months ago:
MarshalNey wrote:Threads themselves could often use some cleaning when they rise above 10 pages, but since this seems impractical to accomplish, they should instead have a really good, short first post. If necessary, put all of the in-depth details on a second post that more interested readers can delve into.
Mapmakers should have a short first post on their thread that has, preferably in this order:
1) A clear, concise explanation of what the map concept and goals are.
2) An outline of what the mapmaker specifically wants to get feedback about; too many mapmakers leave this stuff "buried" in their thread (e.g., 'see my post on page 34'). Take a look at natty_dread's current map threads for examples- LunarWar and Nordic Countries do an excellent job with this.
3) What the foundry mods' current concerns are for this map. I didn't mention this in my previous post, but I think it would help relay to the mods what the mapmaker thinks that they want, and relay to visitors what they can do to help advance the map.
4) A map intended for a layman that comes before any other maps (i.e., before '88' test maps, before wire maps, etc.) or, if you don't have a map made yet, an in-depth explanation of your concept and goals from #1 above.
5) Technical details and previous versions last, preferably hidden as spoilers.
hmmmm, maybe that list could be a little more verbose... Oh here we go! A post from me, also 10 months ago...
MarshalNey wrote:Finally, thread length and the first page of a post. These are serious problems in a lot of map threads. I won't elaborate too much as this post is becoming way too long itself, but obviously you can't expect someone to come into a thread 40 pages long and read it all before posting. So be patient with redundant comments, even if you feel the issue brought up has been put to bed.
The first post should be a table of contents, but after a while it in many threads it ceases to get updated properly. Mapmakers like to post 'previous versions' and '888 versions' to show the development of the map and its current viability. This is good for thoroughness, but this really should always go last on the first post as it's not really going to give casual viewers any useful information.
In many ways, mapmakers construct their first post for the approval of the mods rather than being a primer for the casual viewer. Technical information that means little to the laymen gets more of the focus.
Good heavens, when did I have that much time to type this stuff? If you see the full post, you'll know what I mean.
Anyway, the question about First Posts can be looked at several different ways. Do you want to know:
(1) What one feels the minimum requirements for a First Post should be?
(2) What one feels the average First Post should include?
(3) What one feels the ideal (perfect) First Post would have?
Or all three?
I think it's good not just to include minimums in a Handbook, myself. That way you can give some guidance for mapmakers who are willing to put in more effort. I'm of the firm opinion that the better the First Post, the better/more responsive CA feedback can be, and the better/more responsive Community feedback can be.
Marshal Ney