Live data from Hacker News

MDN Web Docs evolves: Lowdown on the upcoming new platform

hacks.mozilla.org

11–20 of 202 posts

Re: MDN Web Docs evolves: Lowdown on the upcoming new platform

#11
post #5

I am a big fan of jamstack. For a lot of my client's use cases it allows me to save them a lot of money and headaches while delivering a better product, especially with a headless CMS like Netlify CMS

I still don't fully grok the term. Is it a loose/blanket term sorta like 'devops' or is it a more literal prescription of actual requirements and practices?

More "REST" than "JSON". There's no Jamstack spec, no checkboxes to get your Jamstack compliance score. It is a description of a particular set of patterns and practices.

Re: MDN Web Docs evolves: Lowdown on the upcoming new platform

#13
Good to know that the MDN team are still working on the platform and even evolving it (hopefully for the better), despite severe layoffs.

What about the content part of it? Is it the hope that the move to GitHub and PR model will encourage broader community contribution and thus make up for the sad lack of dedicated content writers?

Re: MDN Web Docs evolves: Lowdown on the upcoming new platform

#14
post #12

So they're hoping that they can replace the people they fired with open source contributors working for free.

If the alternative is to close shop and let it die entirely, I don't have an issue with it

It's not like they were extremely profitable and fired people to squeeze an extra buck

Laying off people isn't inherently evil

Re: MDN Web Docs evolves: Lowdown on the upcoming new platform

#15
It is going to be the 5th iteration of CMS/wiki software. Hopefully this is the right one.

1. Netscape DevEdge

2. MediaWiki

3. Deki Wiki (renamed to MindTouch, closed source since 2013)

4. Kuma

5. Yari

There's a nice history here: https://developer.mozilla.org/en-US/docs/MDN_at_ten/History_...

Re: MDN Web Docs evolves: Lowdown on the upcoming new platform

#16
post #12

So they're hoping that they can replace the people they fired with open source contributors working for free.

Man these kind of views bother me so much. They’re taking one of the most (if not, most) useful documentation sources for cross platform web development that benefits them very little, and moving it to a system of open contribution so it can live past the company’s financial problems. And this is your first take?

Re: MDN Web Docs evolves: Lowdown on the upcoming new platform

#17
post #5

I am a big fan of jamstack. For a lot of my client's use cases it allows me to save them a lot of money and headaches while delivering a better product, especially with a headless CMS like Netlify CMS

I still don't fully grok the term. Is it a loose/blanket term sorta like 'devops' or is it a more literal prescription of actual requirements and practices?

Jamstack is essentially a client/cloud model. Instead of client/server/db it is client with CDN and apis/microservices.

Jamstack is static sites/headless CMS, CDN for content/storage/speed, microservices/apis for data/auth/etc focused on speed, pre-rendering, and decoupling for easier swappable parts rather than monolith. [1]

[1] https://jamstack.org/what-is-jamstack/

Re: MDN Web Docs evolves: Lowdown on the upcoming new platform

#19
post #16
post #12

So they're hoping that they can replace the people they fired with open source contributors working for free.

Man these kind of views bother me so much. They’re taking one of the most (if not, most) useful documentation sources for cross platform web development that benefits them very little, and moving it to a system of open contribution so it can live past the company’s financial problems. And this is your first take?

As far as I can see, Mozilla have no reason to be losing money other than their own mismanagement.

Re: MDN Web Docs evolves: Lowdown on the upcoming new platform

#20
post #12

So they're hoping that they can replace the people they fired with open source contributors working for free.

I read it more as they cleaned up the contribution process so that it's easier for people to participate.

But if what you said does happen, then RIP. It's not going to be the same - everyone is too busy writing medium articles to sell their course on udemy to make real contributions for free.

There were a lot of useful guides showing practical applications of features beyond just listing the api spec.

But I guess it'll still be useful as a more approachable wiki to api standards rather than having to go to w3schools (yuck) or the horrible ui of w3c.

Post reply on HN