This is the first of a series of blog posts about MDN, the product I am product manager for. The series discusses MDN’s business case, product strategy, and a series of experiments we can run on MDN in 2015 (and beyond) to help it continue to serve its audience and the web. Many people familiar with MDN will consider some of the following posts obvious; to them I say, “stay with me.” Not all of this will be obvious to everyone. Some may be novel to everyone. Any of it may need clarification or improvement, which I will learn from gentle comments.
- What is MDN?
- Whom is MDN for?
- What are their problems?
- How does MDN solve those problems?
- What does solving those problems accomplish for Mozilla?
- MDN is a strong brand supported a number of products and activities.
- Chief among these is a platform, the documentation wiki, which is also called MDN.
- Within the platform content is huge: MDN’s primary audience visits solely for the content, because the content is valuable. The MDN brand’s authority and the MDN platform’s scale both depend on the MDN content’s quality.
- As an open-source web application serving user-generated content about open standards, contribution overlaps almost every aspect MDN — especially content creation. The MDN content’s quality depends in large part on contribution.
- Various marketing efforts support MDN, strengthening its brand, attracting new visitors, and activating contributors. MDN marketing efforts among developers also support Mozilla’s brand.
- In response to a clear market need, the MDN team is experimenting with some developer-facing services that will be partly supported by the content and platform.
That’s a lot of moving pieces — and we haven’t even begun talking about whom MDN serves and what problems MDN solves for them! Look for answers to those questions and much more in coming posts. As we go I’ll use the above diagram to help contextualize things. More to come! :wq