[Nuxt + Strapi] About the Configuration of the Portfolio Website
- Independent Development
In this article, I would like to provide a high-level explanation of the configuration of our portfolio website.
This website is hosted on AWS, with Strapi serving as the CMS (Content Management System) and Nuxt.js for the front-end.
Before the redesign, we used WordPress as a Headless CMS, and the front-end was developed with Nuxt.js, utilizing CircleCI for Static Site Generation (SSG). Detailed information about this setup can be found in this article, should you wish to explore further.
For this redesign, we decided to stick with Nuxt.js for the front-end, as it was a familiar choice. However, we aimed to build the site with Server-Side Rendering (SSR), which was a new experience for us. Additionally, we wanted to expand our content, including adding a blog. After evaluating several Headless CMS options, we selected Strapi. Strapi allows for highly customizable content creation and has straightforward integration for GraphQL, making it an ideal choice for this project.
Regarding Nuxt.js, we initially used version 2 before the redesign, but we transitioned to version 3 after the revamp. Despite being in the public beta version at the time of implementation, it proved to be relatively smooth to use. We plan to share more insights on this in a separate article.
You can access the design and source code of our deliverables from the links provided below. Please feel free to take a look.