CMX

cmxhub.com · Group blog · on HN since 2014

CMX is a publication about building and growing online communities, with case studies from startups such as Product Hunt and 7 Cups of Tea.

What HN saysHN commenters point to it as a good source of information on community building, though comments don't give detailed opinions on individual posts.
15HN people shared it
3linked it in comments
15stories submitted
240story points
4 years agolast shared
2014people per year2026

Most-shared posts

  1. 1
    7 tools Product Hunt used to build its community
    2 people · 4 points · first shared 2014 · 1 comments on HN
  2. 2
  3. 3
    A look at Assembly, the community that founds companies
    1 people · 64 points · first shared 2014 · 16 comments on HN
  4. 4
  5. 5
  6. 6
  7. 7
  8. 8
  9. 9
  10. 10
    The 7P's of Community
    1 people · 2 points · first shared 2018 · discussion on HN
  11. 11
  12. 12
  13. 13
  14. 14
    Trello Playbook for Launching a Slack Community
    1 people · 1 points · first shared 2017 · discussion on HN
  15. 15
    Product hunt erik torenberg community
    1 people · first shared 2017

What HN people wrote when they linked it

KanyeBest · 2017-06-30
Platzi has a series of videos on this topic. https://courses.platzi.com/classes/build-grow-online-communities/ Edit: Apparently it's no longer free. The course isn't really worth $100 in my opinion, so here's a short writeup of the videos http://cmxhub.com/article/product-hunt-erik-torenberg-community/
murrain · 2015-10-01
There's a lot of good information about community at CMX Hub: http://cmxhub.com/
mary_grace · 2019-04-25
Like panda888888 said, DevRel in an ideal world is less about metrics and more about listening and building relationships with your community, but as we all know, metrics are still necessary to prove business value and to keep the team alive within a company. I wrote a whole book about how to determine and show the business value of DevRel at your particular company (http://persea-consulting.com/book) but there are two main points I'll highlight here: 1) When reporting success to stakeholders at your company, focus less on the work output (how many conferences did you speak at, blogposts did you write, etc.) and more on the goals that those tasks pushed forward. What's the purpose of the blogposts? Are you trying to improve your audience's onboarding experience by writing tutorials or sample applications to help them understand various uses of your product? Are you speaking at conferences for brand awareness purposes or to popularize the key principles that your product is built upon? Focus on those topics instead of "I did `x`." For instance, focus on how many fewer support tickets were decreased as a result of your tutorial or improved documentation. 2) Make sure that your goals are aligned with the company goals. Your team mission should point back to the overarching company goals in a way that it's clear the work that you're doing will further the goals of the company. (Note: If you don't have a team mission, you should! I wrote an article about that here:…

Keyboard shortcuts

/Search
j kNext / previous blog
EnterOpen selected blog
vVisit the blog site
fFollow / unfollow
lSwitch grid / list view
dSwitch dark mode
g hHome
g pTop posts
g tTopics
g fFollowing
g lLiked
g yHistory
g qFAQ
EscBack / close