An Update on MDN Web Docs
&gt; The other areas we have had to scale back on staffing and programs include: Mozilla developer programs, developer events and advocacy, and our MDN tech writing.<p>&gt; We recognize that our tech writing staff drive a great deal of value to MDN users, as do partner contributions to the content. So we are working on a plan to keep the content up to date.<p>The stated rationale for the &quot;re-org&quot; (read, layoffs) was to shore up the financials and explore new revenue opportunities. Here is a novel idea that I will provide at no cost:<p><i>Charge for access to MDN</i>, structure the legal particulars so that revenue goes to pay the tech writing staff, covers operating costs, and provides the excess to the Mozilla Foundation. Use the resulting goodwill and attention as a lead generation mechanism for whatever other projects Mozilla tries to create and charge for.<p>Market validation you say? People won&#x27;t pay for documentation you say? The sole developer of the macOS app Dash[1] makes a fairly decent living selling an app that merely allows you to <i>search freely available documentation offline</i>. MDN has real value that people, myself included, will pay for. Just this week I have referred to MDN documentation at least a couple of hundred times.<p>Charge. Money. For. MDN.<p>And pay the tech writers.<p>[1] <a href="https:&#x2F;&#x2F;kapeli.com&#x2F;dash" rel="nofollow">https:&#x2F;&#x2F;kapeli.com&#x2F;dash</a><p>Edit: wording correction.