From the comment discussion on the question it sounds like you are looking to help people understand how to answer, rather than just teach them to golf. Maybe it would help to have some general guidance on what we like to see in answers.
Personally I am more likely to upvote an answer that is interesting and well explained. This kind of general advice could go in one place (perhaps a blog post), while advice specific to the different question types could go in the individual tag wikis. Links to the tag wikis from the blog post would help new users who may not realise the tag wikis are the place to look. This keeps the blog post a manageable size while still providing further reading.
I like Beta Decay's suggestion of a list of suggested challenges. Easy to hard makes sense for some things, but it may be worth subdividing in other ways too, perhaps into specialist areas. What is easy will depend on a person's previous experience.
If we have a list for code-golf, a list for fastest-code, a list for king-of-the-hill, and so on, these lists could possibly be included at the end of the tag wikis, or they could form separate blog posts to be linked to from the tag wikis and the general blog post.
Some people may like to see a step by step walk through of writing long code and then golfing it down. There are already answers that explain the golfing process in detail, and many that provide golfed and ungolfed code for comparison. Such a guide could give examples of little savings, and then link to the tips tag for further examples, and then also give examples of changing algorithm to give a dramatic saving. This could be followed up with links to answers that give particularly helpful explanations of their workings.
Similar tutorials could be put together for other question types (depending on which ones have people volunteer to write them). People can also indicate here on Meta if they have an area they would particularly like to see a guide for.