blog VS gatsby-starter-default

The output is fully customizable, as it is 100% generated from code. You can change some values here and there, and boom! Generated. I ran it through all the posts of my blog and it quickly replaced many of the blog posts for me.

The full implementation can be found in the source code of this blog on Github

upper@DESKTOP-6JTLCIP:/mnt/c/Users/Usuario/Codes/wsite/oportunidades-ilimitadas$ gatsby new board https://github.com/gatsbyjs/gatsby-starter-default info Creating new site from git: https://github.com/gatsbyjs/gatsby-starter-default.git

{ "name": "gatsby-starter-default", "private": true, "description": "A simple starter to get up and developing quickly with Gatsby", "version": "0.1.0", "author": "Kyle Mathews ", "dependencies": { "babel-plugin-styled-components": "^2.0.7", "gatsby": "^5.7.0", "gatsby-image": "^3.11.0", "gatsby-plugin-google-fonts-with-attributes": "^1.0.8", "gatsby-plugin-google-gtag": "^5.7.0", "gatsby-plugin-image": "^3.7.0", "gatsby-plugin-manifest": "^5.7.0", "gatsby-plugin-robots-txt": "^1.8.0", "gatsby-plugin-sharp": "^5.7.0", "gatsby-plugin-sitemap": "^6.7.0", "gatsby-plugin-styled-components": "^6.7.0", "gatsby-source-filesystem": "^5.5.0", "gatsby-source-wordpress": "^7.7.0", "gatsby-transformer-sharp": "^5.5.0", "react": "^18.2.0", "react-dom": "^18.2.0", "styled-components": "^5.3.6", "universal-cookie": "^4.0.4" }, "devDependencies": { "prettier": "^2.8.3" }, "keywords": [ "gatsby" ], "license": "0BSD", "scripts": { "build": "gatsby build", "develop": "gatsby develop", "format": "prettier --write \"**/*.{js,jsx,ts,tsx,json,md,css}\"", "start": "gatsby develop", "serve": "gatsby serve", "clean": "gatsby clean", "test": "echo \"Write tests! -> https://gatsby.dev/unit-testing\" && exit 1", "deploy": "gatsby clean && gatsy build && gatsby prepend && node deploy" }, "repository": { "type": "git", "url": "https://github.com/gatsbyjs/gatsby-starter-default" }, "bugs": { "url": "https://github.com/gatsbyjs/gatsby/issues" } }

module.exports = { siteMetadata: { title: `Gatsby Default Starter`, description: `Kick off your next, great Gatsby project with this default starter. This barebones starter ships with the main Gatsby configuration files you might need.`, author: `@gatsbyjs`, siteUrl: `https://gatsbystarterdefaultsource.gatsbyjs.io/`, }, plugins: [ `gatsby-plugin-image`, 'gatsby-plugin-postcss', { resolve: `gatsby-source-filesystem`, options: { name: `images`, path: `${__dirname}/src/images`, }, }, `gatsby-transformer-sharp`, `gatsby-plugin-sharp`, { resolve: `gatsby-plugin-manifest`, options: { name: `gatsby-starter-default`, short_name: `starter`, start_url: `/`, background_color: `#663399`, // This will impact how browsers show your PWA/website // https://css-tricks.com/meta-theme-color-and-trickery/ // theme_color: `#663399`, display: `minimal-ui`, icon: `src/images/gatsby-icon.png`, // This path is relative to the root of the site. }, }, ], }

To make it even easier for you, we went ahead and created a Clerk + Gatsby starter repository. It has Clerk integrated with Gatsby's default starter.

First of all, we might have to be familiar with Gatsby as this article will skip over a lot of stuff to get to the point. Gatsby does provide a starter project. Importantly, we can definitely extend the website to have multiple pages such as blog, about, contact, etc.

Check your gatsby-config to see if the static query folder is setup. For example, if it’s an images, you need to setup the path. Check out this

gatsby new happy-paws https://github.com/gatsbyjs/gatsby-starter-default