NextJS
I’ve always wanted to build something on NextJS. Building out the Friction Log website was the perfect opportunity to do so.
- Media available on:
I’ve always wanted to build something on NextJS. Building out the Friction Log website was the perfect opportunity to do so.
About the Tester
The user is me in this case. Some things to note about this log:
- All my React experience has been client-side apps with zero server-side rendering.
- I’ve understood the server-side rendering concept for a while and read up on how NextJS does things, prior to this log.
- I’m very familiar with React
The goal of the log was to take an HTML/CSS template I built and convert it to NextJS.
Logs 5
Friction
Documentation Search
The doc search doesn’t always work. I was searching for Tailwind and it didn’t come up, even though it’s referenced in the docs.
Friction
Tailwind Issues
I had problems using Tailwind out of the box. In hindsight it was a pretty simple path but it wasn't clear out of the gate. Also some of the conventions like _app.js was something I just had to learn (which is expected).
Friction
Wrong error masked an actual mistake
I ran in to a weird behavior where props weren't always present when using getStaticProps. The actual problem was an undefined component but the error told me that my props were undefined, which was completely unrelated.
Delight
The Tutorial
The tutorial is very straightforward, introduced me to the right concepts at the right time, and was easy to navigate.
Delight
The feeling of small complexity
Using NextJS for static content feels a lot less complicated than other similar things like GatsbyJS
