Image-heavy photography portfolio with colorful accents & customizable pages.

  • By Nam Pham
  • Last update: May 24, 2022
  • Comments: 1


Gatsby Starter Portfolio: Jodie

Gatsby Starter Portfolio: Jodie is released under the 0BSD license. GitHub Sponsors Website Follow @lekoarts_de

Image-heavy photography portfolio with colorful accents & customizable pages. Includes adaptive image grids powered by CSS grid and automatic image integration into projects. Using the Gatsby Theme @lekoarts/gatsby-theme-jodie.

Demo Website

Also be sure to check out other Free & Open Source Gatsby Themes and my Personal Website.


  • MDX
  • Fully customizable through the usage of Gatsby Themes (and Theme UI)
  • Create a project by creating an MDX file and dropping the images into the same folder
  • Extensible custom pages
  • Define colors for each page and the sidebar & content will adapt while maintaining WCAG 2 AA contrast ratios
  • SEO (Sitemap, OpenGraph tags, Twitter tags)
  • WebApp Manifest

🚀 Getting Started

Deploy to Gatsby Cloud

1. Create a Gatsby site.

Use git to clone the site and navigate into it:

git clone project-name
cd project-name

2. Install dependencies.

If you use npm 7 or above use the --legacy-peer-deps flag. If you use npm 6 you can use npm install.

npm install --legacy-peer-deps

3. Open the code and start customizing!

Start the site by running npm run develop.

Your site is now running at http://localhost:8000!

If you want to learn more about how you can use a Gatsby starter that is configured with a Gatsby theme, you can check out this shorter or longer tutorial. The tutorials don't exactly apply to this starter however the concepts are the same.

📝 Using and modifying this starter

Important Note: Please read the guide Shadowing in Gatsby Themes to understand how to customize the underlying theme!

This starter creates a new Gatsby site that installs and configures the theme @lekoarts/gatsby-theme-jodie.

Have a look at the theme's README and files to see what options are available and how you can shadow the various components including Theme UI. Generally speaking you will want to place your files into src/@lekoarts/gatsby-theme-jodie/ to shadow/override files. The Theme UI config can be configured by shadowing its files in src/gatsby-plugin-theme-ui/.

Changing the logo

Edit the file at src/@lekoarts/gatsby-theme-jodie/icons/logo.jsx.

Changing your fonts

By default, the underlying theme and thus this starter uses "Work Sans" as its font. It's used throughout the site and set as a font-family on the html element.

If you want to change your default font or add any additional fonts, you'll need to change two things:

  1. The configuration for gatsby-omni-font-loader => Responsible for loading the font CSS files
  2. The Theme UI config and its fonts key (see Theme UI Typography Docs) => Responsible for setting the font-family in the example

After adjusting the configuration for gatsby-omni-font-loader you'll need to shadow the theme's Theme UI config and overwrite the fonts key. For the sake of this explanation it's assumed that you replaced "Work Sans" with "Roboto Mono".

Create a file at src/gatsby-plugin-theme-ui/index.js with the following contents:

import { merge } from "theme-ui";
import originalTheme from "@lekoarts/gatsby-theme-jodie/src/gatsby-plugin-theme-ui/index";

const theme = merge(originalTheme, {
  fonts: {
    body: `"Roboto Mono", monospace`,

export default theme;

As defined in the Theme Specification body is the default body font family.

Another example: You didn't replace "Work Sans" but added "Roboto Mono" additionally since you want to use it for your headings.

Then you'd not overwrite body but add a heading key:

import { merge } from "theme-ui";
import originalTheme from "@lekoarts/gatsby-theme-jodie/src/gatsby-plugin-theme-ui/index";

const theme = merge(originalTheme, {
  fonts: {
    heading: `"Roboto Mono", monospace`,

export default theme;

Customizing the homepage

Both your projects and pages are displayed on the homepage (located at / in the live project and src/components/homepage.tsx in the theme itself). Of course, you can always shadow this and other files to customize the theme to your liking.

However, before completely overriding the homepage you should consider the three available options:

  1. homepagePageLimit
  2. homepageProjectLimit
  3. Shadowing modify-grid.ts

The options 1) and 2) are explained in the theme options -- they limit the number of projects and pages that will randomly be distributed on the page.

Option 3) is a really powerful one! The modifyGrid function is wrapping the entire array of projects & pages before passing it to the render function of the React component. Or in other words: As the name suggests you can modify the items that are passed to the grid on the homepage.

You can achieve this by shadowing modify-grid.ts: Create a file at src/@lekoarts/gatsby-theme-jodie/utils/modify-grid.js and define a default export for modifyGrid.

modifyGrid examples

All code snippets are placed inside src/@lekoarts/gatsby-theme-jodie/utils/modify-grid.js

Default behavior:

const modifyGrid = (data) => data;

export default modifyGrid;

I've also created some resolver templates that you can use. They are exported in resolver-templates.ts. They cover the most common use cases and can give you an idea on what to do with the resolver.

Only pages / Only projects:

onlyPages(data); // const modifyGrid = (data) => onlyProjects(data) export default modifyGrid;">
import {
} from "@lekoarts/gatsby-theme-jodie/src/utils/resolver-templates";

const modifyGrid = (data) => onlyPages(data);
// const modifyGrid = (data) => onlyProjects(data)

export default modifyGrid;

Filter by slug:

filterBySlug(data, ["/about"]); export default modifyGrid;">
import { filterBySlug } from "@lekoarts/gatsby-theme-jodie/src/utils/resolver-templates";

const modifyGrid = (data) => filterBySlug(data, ["/about"]);

export default modifyGrid;


shuffle(data); export default modifyGrid;">
import { shuffle } from "@lekoarts/gatsby-theme-jodie/src/utils/resolver-templates";

const modifyGrid = (data) => shuffle(data);

export default modifyGrid;

Change your static folder

The static folder contains the icons, social media images and robots.txt. Don't forget to change these files, too! You can use Real Favicon Generator to generate the image files inside static.

🤔 Questions or problems?

If you have general questions or need help with Gatsby, please go to one of the support platforms mentioned in Gatsby's documentation. If you have a specific question about this project, you can head to the GitHub Discussions of the repository.

🎓 Learning Gatsby

Looking for more guidance? Full documentation for Gatsby lives on Gatsby's website.


To learn more about Gatsby themes specifically, I recommend checking out the theme docs.


🌟 Supporting me

Thanks for using this project! I'm always interested in seeing what people do with my projects, so don't hesitate to tag me on Twitter and share the project with me.

Please star this project, share it on Social Media or consider supporting me on Patreon or GitHub Sponsor!



  • 1

    Configure Renovate

    Mend Renovate

    Welcome to Renovate! This is an onboarding PR to help you understand and configure settings before regular Pull Requests begin.

    🚦 To activate Renovate, merge this Pull Request. To disable Renovate, simply close this Pull Request unmerged.

    Detected Package Files

    • package.json (npm)


    🔡 Renovate has detected a custom config for this PR. Feel free to ask for help if you have any doubts and would like it reviewed.

    Important: Now that this branch is edited, Renovate can't rebase it from the base branch any more. If you make changes to the base branch that could impact this onboarding PR, please merge them manually.

    What to Expect

    With your current configuration, Renovate will create 5 Pull Requests:

    chore(deps): update dependency patch-package to v6.5.0
    • Schedule: ["at any time"]
    • Branch name: renovate/patch-package-6.x
    • Merge into: master
    • Upgrade patch-package to 6.5.0
    fix(deps): update dependency @​lekoarts/gatsby-theme-jodie to v5
    • Schedule: ["at any time"]
    • Branch name: renovate/lekoarts-gatsby-theme-jodie-5.x
    • Merge into: master
    • Upgrade @lekoarts/gatsby-theme-jodie to ^5.0.0
    fix(deps): update dependency gatsby-omni-font-loader to v2
    • Schedule: ["at any time"]
    • Branch name: renovate/gatsby-omni-font-loader-2.x
    • Merge into: master
    • Upgrade gatsby-omni-font-loader to ^2.0.0
    fix(deps): update gatsby monorepo (major)
    fix(deps): update react monorepo to v18 (major)
    • Schedule: ["at any time"]
    • Branch name: renovate/major-react-monorepo
    • Merge into: master
    • Upgrade react to ^18.0.0
    • Upgrade react-dom to ^18.0.0

    🚸 Branch creation will be limited to maximum 2 per hour, so it doesn't swamp any CI resources or spam the project. See docs for prhourlylimit for details.

    ❓ Got questions? Check out Renovate's Docs, particularly the Getting Started section. If you need any further assistance then you can also request help here.

    This PR has been generated by Mend Renovate. View repository job log here.