Jeffrey Shen's Personal Website

Personal site and portfolio created with GatsbyJS using React. New Gatsby site is in site and old-site has old static site with HTML, CSS files.

Dependency maintenance

The Gatsby source is in site/ on develop; master contains the published GitHub Pages output. Use Node 24 (cd site && nvm install && nvm use).

cd site
npm ci
npm test          # full production build, including all page queries and SSR
npm audit         # review direct and transitive security advisories
npm outdated

Pull requests and pushes to develop run the production build in GitHub Actions. Dependabot checks npm weekly, groups Gatsby and React updates, and checks Actions monthly. Review major-version changes and the build result before merging. npm run deploy builds and publishes to master; a successful local build alone does not update the live site.

React remains on 18.3.1 for compatibility with the site's existing React Helmet and default-props usage. A React 19 upgrade requires a separate compatibility pass. Unused PDF parsing and font-preload tooling have been removed; the downloadable PDFs in site/static/notes continue to be copied directly into the published site.

🚀 Quick start

Deploy Site

Deploy the updated site.

  cd site
  npm run deploy

Start developing.

Navigate into your new site’s directory and start it up.

    cd site/
    gatsby develop

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

_Note: You'll also see a second link: _`http://localhost:8000/___graphql`_. This is a tool you can use to experiment with querying your data. Learn more about using this tool in the [Gatsby tutorial](https://www.gatsbyjs.com/tutorial/part-five/#introducing-graphiql)._

🧐 What's inside?

A quick look at the top-level files and directories you'll see in a Gatsby project.

.
├── node_modules
├── src
    ├── components
    ├── pages
    ├── files
    ├── images
    ├── styles
├── .gitignore
├── .prettierrc
├── gatsby-browser.js
├── gatsby-config.js
├── gatsby-node.js
├── gatsby-ssr.js
├── LICENSE
├── package-lock.json
├── package.json

1. /node_modules: This directory contains all of the modules of code that your project depends on (npm packages) are automatically installed.

2. /src: This directory will contain all of the code related to what you will see on the front-end of your site (what you see in the browser) such as your site header or a page template. src is a convention for “source code”.

3. .gitignore: This file tells git which files it should not track / not maintain a version history for.

4. .prettierrc: This is a configuration file for Prettier. Prettier is a tool to help keep the formatting of your code consistent.

5. gatsby-browser.js: This file is where Gatsby expects to find any usage of the Gatsby browser APIs (if any). These allow customization/extension of default Gatsby settings affecting the browser.

6. gatsby-config.js: This is the main configuration file for a Gatsby site. This is where you can specify information about your site (metadata) like the site title and description, which Gatsby plugins you’d like to include, etc. (Check out the config docs for more detail).

7. gatsby-node.js: This file is where Gatsby expects to find any usage of the Gatsby Node APIs (if any). These allow customization/extension of default Gatsby settings affecting pieces of the site build process.

8. gatsby-ssr.js: This file is where Gatsby expects to find any usage of the Gatsby server-side rendering APIs (if any). These allow customization of default Gatsby settings affecting server-side rendering.

9. LICENSE: This Gatsby starter is licensed under the 0BSD license. This means that you can see this file as a placeholder and replace it with your own license.

10. package-lock.json (See package.json below, first). This is an automatically generated file based on the exact versions of your npm dependencies that were installed for your project. (You won’t change this file directly).

11. package.json: A manifest file for Node.js projects, which includes things like metadata (the project’s name, author, etc). This manifest is how npm knows which packages to install for your project.

12. README.md: A text file containing useful reference information about your project.

🎓 Learning Gatsby

Looking for more guidance? Full documentation for Gatsby lives on the website. Here are some places to start:

• For most developers, we recommend starting with our in-depth tutorial for creating a site with Gatsby. It starts with zero assumptions about your level of ability and walks through every step of the process.

• To dive straight into code samples, head to our documentation. In particular, check out the Guides, API Reference, and Advanced Tutorials sections in the sidebar.

💫 Deploy