Articles on structuring objects in pre and post ES2015 syntactic sugar
mikaelbr opened this issue · comments
Should we have an article covering prototypes and classes for a more modern approach? Explaining both the fundamentals/how it works, and how the ES2015 syntax differs?
Kyle Simpson or Eric Elliot probably has something
@mikaelbr @mollerse Looked at these https://github.com/getify/You-Dont-Know-JS#titles? I haven't yet.
I've read all of them. Really liked most of it. Perhaps it's for more advanced/"conservative"/extra interested people, but it gives a very detailed explaination and after reading it twice I feel it's really given me value.
I'd prefer Kyle Simpsons work (YDKJS) over Eric Elliot, I think. It does much more into depth, and promotes learning javascript thoroughly. Which I think is something we also should encourage.
Read two of the titles (scope & closures, this & Object prototypes), really enjoyed both. As @mikaelbr said, they are extremely thorough and is perhaps better suited for intermediate devs looking to move into expert.
Hm, maybe we should have an "In-depth" section? For the low-level, advanced stuff. I know I had some articles last time around that didn't fit with the rest because they went "way too far", but that could be an awesome thing for its own category.
One thing I would like from the new site is different grouping of articles (as mentioned before). By having all articles as data, we can label the different articles with a "difficulty level", a topic, and more. And use that data to create different sections.
Maybe create an issue on creating a json format for this, @mikaelbr? Also, it would be awesome if you have ideas on how we could structure it.
Also, it would be awesome if you have ideas on how we could structure it.
Thinking of how to structure it / visualise it on the page? I haven't quite gotten there yet, but I'll look around for some inspiration.
I mostly thought about the json, but of course it would also be awesome to find some inspiration for the how to visualize it on the page.