DEV Community

Cover image for Next.JS is awesome!
kapeel kokane
kapeel kokane

Posted on

20 5

Next.JS is awesome!

Hey folks,

I recently stumbled upon a requirement: A blog/portfolio website for all my content creation activities. I wanted it to be a one stop destination for all my content.

Purpose

Basically, there are the different places where I create content:

  • My Youtube channel, where I create animated tech videos.
  • This dev.to blog where you are reading the current article.
  • My twitter account where I create sketchnotes related to Javascript.

Product Requirement

The product requirement was simple - A home page where users would land and get a summary/dashboard of the best content from all the 3 places mentioned above. And then a side-menu where they can naviagte between a detailed list of all of these.

Technical Requirement

My tech requirement was different. I have been working with react for quite some time now but this time around, I thought to experiment with SSR (Server side rendering). I wanted to experience the power of pre-rendering and also get advantage of the SEO that comes along with SSR. I know that gatsby and next were two of the most famous ways to accomplish the above.

tl;dr - I checked out next.JS first and fell in love with it (Still haven't looked at Gatsby). 😛

Next.JS - What I was looking for

So what did I find in next.js?

I found exactly what I was looking for:

  • I would still code my SSR blog with react! ❤️
  • The pre-rendered pages
  • automatic routing based on file paths (how aweosme is that!)
  • Sass support
  • Zero configuration deployment with vercel!

It was all too good to be true. I was able to push the first build of my blog (rather a raw build) to production in about 2 hours in total from the point of creating the repo. And the cherry on top: vercel even provides you a free .now.sh domain!

I'll still hold off from sharing the first build of my blog as it is still a work in progress. But the experience so far has been flawless! fingers crossed. 🤞🏽

Kudos team vercel!
Cheers!

Sentry blog image

How to reduce TTFB

In the past few years in the web dev world, we’ve seen a significant push towards rendering our websites on the server. Doing so is better for SEO and performs better on low-powered devices, but one thing we had to sacrifice is TTFB.

In this article, we’ll see how we can identify what makes our TTFB high so we can fix it.

Read more

Top comments (7)

Collapse
 
shubhamk profile image
Shubham Kamath

You got some interesting YouTube videos on your channel. Waiting for more on next!

Collapse
 
kokaneka profile image
kapeel kokane

Thanks a lot! Don't forget to subscribe to the channel :)

Collapse
 
shubhamk profile image
Shubham Kamath

Already did and added videos to my list which I'll be watching this weekend 😬

Thread Thread
 
kokaneka profile image
kapeel kokane

Awesome!

Collapse
 
jmojico profile image
Julian Mojico

oowwww ...I was expecting some insights about NextJs....and to see your blog in action.
Let us know when it's ready, I look forward to read your next article!

Collapse
 
kokaneka profile image
kapeel kokane

Thanks Julian. The blog will be ready in a week. Will write another article when done. :)

Collapse
 
souksyp profile image
Souk Syp.

Did you try Sapper after Next? I thought I love Next but for performance reasons I picked Sapper in the end.

nextjs tutorial video

Youtube Tutorial Series 📺

So you built a Next.js app, but you need a clear view of the entire operation flow to be able to identify performance bottlenecks before you launch. But how do you get started? Get the essentials on tracing for Next.js from @nikolovlazar in this video series 👀

Watch the Youtube series

👋 Kindness is contagious

Please leave a ❤️ or a friendly comment on this post if you found it helpful!

Okay