On Hold SE Community Devs:
The short of it is, it's kinda on us to make something that works, and we don't really do that. There isn't any real proper integration between the systems and the authors suffer as a result of it. Ultimately leading to fairly ill fates to most all of the blogs. We're looking to fix all this but it's going to take some time, and we feel that it'd be better that we have people wait (or perhaps even prepare) for a more complete blog experience that we'll offer down the road.
Since all feedback on phase-1 has been positive (so far), it makes sense to (tentatively) begin phase 2 discussions: Defining the scope of what the blog will be.
This will help cement the tentative discussion in phase 1, and will also help those people who are uncertain whether to support the blog idea, or not.
This is a description of what 'defining the scope' means:
Is the blog about the site? Is it about the site’s topic? Is it about the industry around the topic? Keep in mind the audience of your community and their interests. Another generic blog about may not be all that interesting. A community blog should be interesting to both current members and potential new members.
How do you think the blog should be defined?
In this question, I recommend we use a system similar to what has been used in challenge meta questions:
- one idea in each answer.
- up-vote the idea if you believe that sort of topic is 'within scope' for the Blog.
- down-vote if you believe it should be avoided (but please add a comment explaining your reasoning).
By setting it up this way, and because all answers to this question will be 'community wiki', there is no reason why you should not 'brainstorm' and come up with all sorts of ideas.... good, dubious, and just-for-discussion.
(and hey, some of you have never downvoted before - here's your chance to ... too.... ;-)
For your 'back-reference' this is the recommended procedure for establishing a site blog on Stack Exchange: