I'm always rebuilding my portfolio in different ways as a way of learning the latest tools. This site has been rebuilt multiple times. From a humble old Wordpress site, to a Single page React App with functional CSS classes, to Styled Components and Styled System, to being Prismic and Redux managed. But this last iteration I've migrated to make use of Gatsby and GraphQl (with Prismic content).
Note: This gatsby-starter-portfolio-bella project helped me a lot with this latest iteration, to understand how to integrate Gatsby and Prismic with GraphQl.
All of the UI has been styled with the Styled Components and Styled System.
Design system utilities for styled-components and other css-in-js libraries. Add style props that hook into your own theme. Responsive prop values for quickly setting responsive font-size, margin, padding, width, and more. Check the github page here.
In the project directory, you can run:
npm run dev
Runs the app in the development mode.
Open http://localhost:8000 to view it in the browser.
npm run build
Builds the site for production to the
Checks for esLint errors
Auto fixes any esLint errors where possible
A quick look at the top-level files and directories you'll see in this Gatsby project.
. ├── node_modules ├── src ├── .gitignore ├── .eslintrc ├── gatsby-browser.js ├── gatsby-config.js ├── gatsby-node.js ├── gatsby-ssr.js ├── package-lock.json ├── package.json ├── README.md
/node_modules: This directory contains all of the modules of code that your project depends on (npm packages) are automatically installed.
/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.
srcis a convention for “source code”.
.gitignore: This file tells git which files it should not track / not maintain a version history for.
.eslintrc: This is a configuration file for Eslint. Eslint is a tool to help keep the formatting of your code consistent.
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.
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).
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.
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.
package.jsonbelow, 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).
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.
README.md: A text file containing useful reference information about this project.
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 the documentation. In particular, check out the Guides, API Reference, and Advanced Tutorials sections in the sidebar.