Given that our little corner of the "interwebs" was recently promoted to a full StackExchange network site, I thought we might commemorate the occasion by launching a community-drive Blog Overflow for Magento StackExchange. If you're only recently discovering this SE feature you can quickly checkout the other current community driven blogs hosted on the SE platform and learn more about the original vision behind adding this feature to the core SE Experience in this blog post. There's also a SE Chat dedicated to Community SE Blogs.
To this I say "Pish! Posh! And Likewise Phooey!" The #RealMagento community NEVER shies away from a challenge!
All kidding aside, we have a unique user base - we develop some of the most complex software deployed in the world on a daily basis powering nearly 1/4 of all e-commerce transactions. Our ranks are overflowing with some of the most innovative and hard-working people in ANY online community. Not so sure? Take a minute to check this out. And then compare it to the grandaddy of them all. There's a tremendous amount of overlap for a SE community that just exited beta a few weeks ago.
I'm officially volunteering to start the effort off and will maintain whatever role you feel appropriate and will happily accept any and all offers of assistance in any capacity whatsoever. But I'll commit to owning getting this effort off the ground and enlisting a core team of co-conspirators.
I have no doubt we can address the concerns raised not only for our own community blog but also assist the SE team on translating our soon-to-be success into a broader set of guidelines to drive the deeper integration of this feature across other SE communities.
So, the challenge, should you choose to accept it:
Vote on this question to show your endorsement / rejection of the core concept of a Community Magento SE Blog.
Next provide your input on the following items based on the original announcement post...
Raise the idea on the child meta. A community blog needs the involvement of community members. These blogs don’t exist to be the personal blog of a community member. They are both for and run by the community. It needs to be something the community collectively wants and will cultivate.
Define the scope and purpose of the blog. Is the blog about the site? Is it about the site’s topic? Is it about the industry the topic? Keep in mind the audience of your community and their around 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.
Recruit contributors. Who will write entries for the blog? Starting a blog is a bit like going through the buffet line. Be realistic – don’t let your eyes be bigger than your stomach. Think seriously about if and how often you will be able to contribute a blog post, including research/prep time. The more contributors there are, the less frequently each contributor needs to post. One post a month is a much easier to stomach than a couple posts every week.
Plan a schedule. Given the results of steps #2 and #3, think about a week, posted Mondays? Will there be posts on Tuesdays and posts on Fridays? You don’t need to be pushing out posts daily, but you should post at least once a week.a rough idea of a schedule for the blog. Will there be one post
We need to engage GraceNote and share our discussion with the SE team to see if our initial efforts are worthy of a temporary lift of the new-blog embargo.