Newsletter
Join the Community
Subscribe to our newsletter for the latest news and updates
Personal portfolio site built with Next.js, ChakraUI and Framer Motion, deployable on Netlify.

A customizable Jekyll portfolio theme with about, portfolio, and tools sections, easily configured via _config.yml.
KL Portfolio is a TypeScript-based personal portfolio website template built on Next.js, ChakraUI, and Framer Motion, designed to present a developer's bio, projects, and contact links, and deployed on Netlify's free tier.
KL Portfolio is a static personal portfolio site created by developer KL Lawingco as a v2 rewrite of an earlier template-based site. It uses Next.js as a static site generator, ChakraUI for the component library, Framer Motion for animations, and TypeScript throughout. The site currently shows personal details and links out to dev.to for blog posts, with a future plan to host a native blog. The production build is deployed on Netlify's free tier, with build status tracked via a Netlify badge.
yarn install and yarn dev starts a local dev server at http://localhost:3000..nvmrc file for use with nvm use.netlify.toml is required; Netlify handles the build after merging to master.To run locally, clone the repository, run yarn install (or just yarn) to install dependencies, then yarn dev to start the development server at http://localhost:3000. For deployment, there is no special configuration: the site is set up in the Netlify dashboard, and pushing a feature branch to the master branch triggers a new build.
The project requires at least Node v12, but Node v14 LTS is the recommended version. A .nvmrc file is included, so you can run nvm use to automatically switch if you have nvm installed.
The README states that the project heavily favors Yarn over npm. While npm install might work, the documented commands and workflow all use Yarn, so it's safer to stick with Yarn.
The logo and avatar are custom-made by KojiroArt, a friend of the author. They are not part of a stock icon set, so if you reuse them in your own deployed portfolio, consider replacing them with your own branding.
Not yet. The site currently uses dev.to links for articles. The author explicitly mentions planning to add a native blog in the future, but for now external links are used.
