👔 Portfolio thingy, built with Gatsby https://matthiaskretschmann.com
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
 
Matthias Kretschmann 0ed52b4242
imports cleanup
2 days ago
.github use Node.js v18 3 months ago
_content content updates 2 days ago
public bump json5 2 days ago
scripts imports cleanup 2 days ago
src fix icon spacing 5 days ago
tests imports cleanup 2 days ago
.codeclimate.yml readme updates 1 week ago
.editorconfig put back editorconfig 1 week ago
.env.example switch tracking 3 months ago
.eslintrc.json Migrate to Next.js + TypeScript (#1038) 3 months ago
.gitignore new favicon script 3 months ago
.nvmrc use Node.js v18 3 months ago
.prettierrc put back editorconfig 1 week ago
.stylelintrc simplify stylelint/prettier setup 3 years ago
LICENSE documentation, switch to Travis 5 years ago
README.md readme updates 1 week ago
next-env.d.ts Migrate to Next.js + TypeScript (#1038) 3 months ago
next.config.js new favicon script 3 months ago
package-lock.json bump json5 2 days ago
package.json package updates 5 days ago
tsconfig.json Migrate to Next.js + TypeScript (#1038) 3 months ago

README.md

👔 Portfolio thingy.

matthiaskretschmann.com



🎉 Features

The whole portfolio is a React-based single page app built with Next.js in Typescript, using only statically generated pages.

If you are looking for the former Gatsby-based app, it is archived in the gatsby-deprecated branch.

💍 One data file to rule all pages

All displayed project content is powered by one YAML file where all the portfolio's projects are defined. The project description itself is transformed from Markdown written inside the YAML file into HTML on build time.

Next.js automatically creates pages from each item in that file utilizing the [slug].tsx template.

🖼 Project images

All project images live under public/images and are automatically attached to each project based on the inclusion of the project's slug in their filenames.

Next.js with next/image generates all required image sizes for delivering responsible, responsive images to visitors, including lazy loading of all images. For this to work, images are analyzed on build time and various image metadata is passed down as props.

🐱 GitHub repositories

The open source section at the bottom of the front page shows selected GitHub repositories, sourced from GitHub.

On build time, all my public repositories are fetched from GitHub, then filtered against the ones defined in content/repos.yml, sorted by the last push date, and provided via the pageContext of the front page.

If you want to know how, have a look at the respective components:

📍 Location

On client-side, my current and, if known, my next physical location on a city level is fetched from my (private) nomadlist.com profile and displayed in the header.

Fetching is split up into an external serverless function, a hook, and display component. Fetching is done with a serverless function as to not expose the whole profile response into the browser.

If you want to know how, have a look at the respective components:

💅 Theme switcher

Includes a theme switcher which allows user to toggle between a light and a dark theme. Switching between them also happens automatically based on user's system preferences. Uses next-themes under the hood.

If you want to know how, have a look at the respective component:

🏆 SEO component

Includes a SEO component which automatically switches all required meta tags for search engines, Twitter Cards, and Facebook OpenGraph tags based on the browsed route/page.

If you want to know how, have a look at the respective component:

📇 Client-side vCard creation

The Add to addressbook link in the footer automatically creates a downloadable vCard file on the client-side, based on data defined in content/meta.yml.

If you want to know how, have a look at the respective component:

💎 Importing SVG assets

All SVG assets will be converted to React components with the help of @svgr/webpack. Makes use of SVGR so SVG assets can be imported like so:

import Logo from './components/svg/Logo'
return <Logo />

🍬 Typekit component

Includes a component for adding the Typekit snippet.

If you want to know how, have a look at the respective component:

🤓 Scripts

🎈 Add a new project

To add a new project, run the following command. This adds a new item to the top of the projects.yml file, creating the title & slug from the argument:

npm run new -- "Hello"

Then continue modifying the new entry in _content/projects.yml.

Finally, add as many images as needed with the file name format and put into public/images/:

SLUG-01.png
SLUG-02.png
SLUG-03.png
...

🌄 Favicon generation

This generates all required favicon sizes from:

  • src/images/favicon-512.png
  • src/images/favicon.svg (handcrafted, adaptive based on OS theme)

Also creates a web manifest.

npm run favicon

Development

git clone git@github.com:kremalicious/portfolio.git
cd portfolio/

# GITHUB_TOKEN is required for some parts
# See https://docs.github.com/en/github/authenticating-to-github/creating-a-personal-access-token
cp .env.sample .env
vi .env

npm i
npm start

🔮 Linting

ESLint, Prettier, and Stylelint are setup for all linting purposes:

npm run lint

To automatically format all code files:

npm run format

👩‍🔬 Testing

Test suite is setup with Jest and react-testing-library.

To run all tests, including type checking and linting of all files:

npm test

Most test files live beside the respective component. Testing setup, fixtures, and mocks can be found in the tests/ folder.

🚚 Deployment

Every branch or Pull Request is automatically deployed by Vercel with their GitHub integration, where the main branch is automatically aliased to matthiaskretschmann.com. A link to a preview deployment will appear under each Pull Request.

A backup deployment is also happening to a S3 bucket, triggered by pushes to main and executed via GitHub Actions. The deploy command simply calls the scripts/deploy-s3.sh script, syncing the contents of the public/ folder to S3:

npm run deploy:s3

Upon live deployment, deploy script also pings search engines. GitHub requires the following environment variables to be setup for successful deployments in the repository secrets:

  • AWS_ACCESS_KEY_ID
  • AWS_SECRET_ACCESS_KEY
  • AWS_DEFAULT_REGION

🏛 Licenses

© Copyright 2022 Matthias Kretschmann

All images and projects are plain ol' copyright, most displayed projects are subject to the copyright of their respective owners.

Don't care if you fork & play with it, but you're not allowed to publish anything from it as a whole without my written permission. Also please be aware, the combination of typography, colors & layout makes up my brand identity. So please don't just clone everything, but rather do a remix!

All the rest, like all code and documentation, is under:

The MIT License

Full MIT license text