4 ms·

Who will add updated content without the tech writers? It is probably too much to expect the core engineering team to also double as the doc writing team in the

Who will add updated content without the tech writers? It is probably too much to expect the core engineering team to also double as the doc writing team in the longer term. Sounds like they're planning to basically hand MDN over to either an independent foundation or consortium setup just for it, or let MS/Google take stewardship (Apple prominently but perhaps unsurprisingly missing from the Advisory board)... Whatever happens I hope the docs are not left to languish outdated and progressively less useful. MDN is literally the wikipedia for web developers. I also don't see why efforts can't be made to monetise the site with contextual ads. Hosting reasonable ads is better than simply dying off for lack of self sufficiency. If the issue is because of ties to the non-profit foundation then changes can be made...

deleted 6y ago
[deleted]
kinlan 6y ago
My team (Chrome DevRel) is a member of the PAB, I'm looking forward to this week's notes being released in public. We're looking at many options to help secure the future for MDN with Mozilla. In terms of who will add content, we still have our tech writers contributing. But the current volume of content across the site will be lower. My personal opinion is that whilst MDN has an amazing community of people who write for it, it needs a permanent staff to ensure the reference materials are suitable for developers. I want our team to work out how we can get back to having a permanent staff to support MDN and have that staff be agnostic to browser vendors.