Nintendo Direct

Ncom 2.0

Microsites

Smash Bros.

Global Nav

T-Mobile

Sorce

Ncom POC

POC = proof of concept. It was time to move off of our legacy systems completely. To get ready for this I created a simple, but feature rich POC for all of Nintendo.com. This POC included, a custom built Sanity CMS, product detail pages, homepage, nintendo directs, whats new articles, and a custom page builder. Building Nintendo.com from the ground up, this became the foundation of the current Nintendo.com.

Sanity Next.js POC

POC = proof of concept. It was time to move off of our legacy systems completely. To get ready for this I created a simple, but feature rich POC for all of Nintendo.com. This POC included, a custom built Sanity CMS, product detail pages, homepage, nintendo directs, whats new articles, and a custom page builder. Building Nintendo.com from the ground up, this became the foundation of the current Nintendo.com.

Page builder was a fully authorable page builder. An author could select which components they wanted on the page, and move them around into any order. I created a parser that would sift through the final result, and used components to place each prop, and data filled component onto the page.

Page builder

Page builder was a fully authorable page builder. An author could select which components they wanted on the page, and move them around into any order. I created a parser that would sift through the final result, and used components to place each prop, and data filled component onto the page.

For each content type that was authorable, it was very simple to create a listing page. Using already existing content, and a graph call, you could stand up a listing page without any additional authoring.

Product listing pages

For each content type that was authorable, it was very simple to create a listing page. Using already existing content, and a graph call, you could stand up a listing page without any additional authoring.

Game data would normally come from another system, but it was easy enough to include it in my POC. From here I was able to demonstrate how these content types could be re-used across the site.

Game data

Game data would normally come from another system, but it was easy enough to include it in my POC. From here I was able to demonstrate how these content types could be re-used across the site.

The key to a successfull CMS. Reusing content was made easy. Here for example, was Nintendo Direct pages using product info, for each game that is mentioned. For authors, all you had to do was select which products you wanted, instead of authoring each tile manually.

Reusable content

The key to a successfull CMS. Reusing content was made easy. Here for example, was Nintendo Direct pages using product info, for each game that is mentioned. For authors, all you had to do was select which products you wanted, instead of authoring each tile manually.

I used Next.js (react), along with fastly for hosting and GraphQl. I used Sanity to create the authorable interface. The full version of our new Nintendo.com uses all of these except for Sanity. While our team found it was missing some features, I highly recommend it. Sanity is awesome.

Tech stack

I used Next.js (react), along with fastly for hosting and GraphQl. I used Sanity to create the authorable interface. The full version of our new Nintendo.com uses all of these except for Sanity. While our team found it was missing some features, I highly recommend it. Sanity is awesome.