Nintendo Direct

Microsites

Smash Bros.

Ncom POC

Global Nav

T-Mobile

Sorce

Ncom 2.0

It was finally time to move off of our old legacy systems and to a new CMS - AEM (Adobe Experience Manager). As a dev team, this wasn't our pick, but it was pitched to the business, and they wanted it enough to go against our recommendation.

Legacy Migration

It was finally time to move off of our old legacy systems and to a new CMS - AEM (Adobe Experience Manager). As a dev team, this wasn't our pick, but it was pitched to the business, and they wanted it enough to go against our recommendation.

Nintendo.com has a lot, of pages. Our goal was to move them all over into the new CMS, so they they could be authorable, and devs could finally be free from making content changes. Nintendo.com includes: homepage, store, game pages(7000+), news articles, hardware pages, and much more.

A massive migration

Nintendo.com has a lot, of pages. Our goal was to move them all over into the new CMS, so they they could be authorable, and devs could finally be free from making content changes. Nintendo.com includes: homepage, store, game pages(7000+), news articles, hardware pages, and much more.

With so many pages to migrate we needed a new strategy. Re-usable components. I created our initial storybook, which we used as a place to host our components, as well as a source-of-truth for non-dev's to go, and see what components exist.

A new strategy

With so many pages to migrate we needed a new strategy. Re-usable components. I created our initial storybook, which we used as a place to host our components, as well as a source-of-truth for non-dev's to go, and see what components exist.

We created the components to take on many forms. After the component was deployed, it was hooked up to AEM, so that a content author could add it to any page, with any appearance.

Components all across Nintendo.com

We created the components to take on many forms. After the component was deployed, it was hooked up to AEM, so that a content author could add it to any page, with any appearance.

Another priority of the migration was to integrate more personalization. We connected with the Business Analytics team to use their data to render smart lists based on users account information.

Personalization

Another priority of the migration was to integrate more personalization. We connected with the Business Analytics team to use their data to render smart lists based on users account information.

Created a user wish list. From anywhere on Nintendo.com you can click a heart to add games to your wishlist, and view them here.

Wish List

Created a user wish list. From anywhere on Nintendo.com you can click a heart to add games to your wishlist, and view them here.

Also included personalized game rails if wish list was empty.

Wish List

Also included personalized game rails if wish list was empty.

We reached a point that we had enough of our common use cases covered by components, that an author could build a page completely by scratch, with no help from dev required at all. The Events page was one example of this.

Fully authorable

We reached a point that we had enough of our common use cases covered by components, that an author could build a page completely by scratch, with no help from dev required at all. The Events page was one example of this.

Small simple pages were easier to stand up for the marketing team. This was another example of a small page to download zoom backgrounds we made when the pandemic work from home policies were going into effect.

Fully authorable

Small simple pages were easier to stand up for the marketing team. This was another example of a small page to download zoom backgrounds we made when the pandemic work from home policies were going into effect.