I spent a good amount of time learning Nuxt.js which caught my attention recently. I walked through the documentation and tutorials and came across some concepts in the framework configuration that seemed unclear and contradictory to me. Also, while browsing StackOverflow, I found out, I wasn't the only one incomprehensive, confused unicorn in this topic. The whole concept of the configuration was hard to grasp for me, so once I mastered it myself, I thought it might be a good idea to share it and write an article about it, just for the sake of simplification for other fellow developers.
So I wrote a nice article with all the necessary explanations and graphics and I sent it to the framework's Developer Advocate for review and fact-checking (thank you Debbie ;)) only to find out all my findings and pieces of advice originated from the old documentation that's going to be replaced in a little time. So even before publishing, my article had been obsolete 🤦♂️.
After my initial consternation and checking the new docu it turned out the content fitted nicely into my article with just small necessary changes, but I could have made my life easier if I had used the latest documentation.
Lesson learned: When learning new programming stuff, make sure to follow the latest documentation.
Clickbait: Are you wondering what my article was about? Check Demystify Nuxtʼs
Originally published at dev.to.