sungik-choi/gatsby-starter-apple

🍎 Gatsby blog starter kit with beautiful responsive design

gatsby-starter-apple's Issues

Implement Issue <-> Post automation

Ideation

1. Set Git repository (like this repository, contain blog source code)
2. Write Issue (will be a blog post)
3. Run Github Action
4. GET Issue and convert it to a markdown file
5. Add this file to the blog post directory
6. Release
7. This issue will be comment storage (see also: https://utteranc.es/)

Gatsby Cloud end of service

Demo pages can't be viewed via https://apple.gatsbyjs.io/ , because Gatsby Cloud terminated its services.
Will you move to the demo page to other hosting service like Netlify?

Add Compact(No Thumbnail) Design

Add Translation(i18n)

Add ko, en translation file

Add dynamic og image

New language support

Great blog theme made by you!
I tried to add system verilog and verilog language support by following all the links.
Things I have done-

npm install eirikpre/VSCode-SystemVerilog

Then I added the following lines in gatsby-config.js-
{
resolve: `gatsby-remark-vscode`,
options: {
theme: 'Github Light Theme', // Or install your favorite theme from GitHub
extensions: ['systemverilog'] //This is from the name in package.json
}
},

And in the actual post section I made-

```systemverilog
{...code...}
```

But still the syntax highlighting is not showing up. Thanks in advance.

Upgrade to Gatsby 5

Hello there,

Vitaliy (Senior Engineering Manager) from Gatsby here. Thank you for creating this great starter! Since your starter is listed on our official library (https://www.gatsbyjs.com/starters/), it is important to keep it on the latest major release of Gatsby. Doing so ensures your starter will continue to be listed in the library.

If you haven’t seen the news already, we have released a beta version of Gatsby 5 and are on track to release the GA version in November. It would be great if you can upgrade this starter from v4 to v5 by then. Here are the docs on how to migrate: https://v5.gatsbyjs.com/docs/reference/release-notes/migrating-from-v4-to-v5/

Let us know if you have any questions. Thanks again!

Infinite loop

Using node 18.16.1, yarn 3.
Overall the site works, which is great.

I can build it, use develop, and serve.

I have noticed though during yarn develop, there seems to be an infinite loop happening. If this is supposed to be like this, then just disregard.

I have confirmed this is happening on both MacOS Ventura and Windows 11, WSL, with Ubuntu 22.
the file ~/src/gatsby.types.d.ts is being re-written over and over.

yarn serve does not produce any loops.

This is the loop:

info Total nodes: 172, SitePage nodes: 13 (use --verbose for breakdown)
verbose Number of node types: 9. Nodes per type: Directory: 25, File: 55, GRVSCCodeBlock: 15, ImageSharp: 6, MarkdownRemark: 5, Site: 1, SiteBuildMetadata: 1, SitePage: 13, SitePlugin: 51
verbose Checking for deleted pages
verbose Deleted 0 pages
verbose Found 0 changed pages
success Checking for changed pages - 0.001s
verbose Transition to "recreatingPages" > "done"
verbose Transition to "runningQueries"
success onPreExtractQueries - 0.001s
verbose Re-Generating fragments.graphql & TS Types
success extract queries from components - 0.068s
verbose Transition to "runningQueries" > "waitingPendingQueries"
verbose Wrote fragments.graphql file to .cache
verbose Transition to "runningQueries" > "writingRequires"
success write out requires - 0.002s
verbose Transition to "runningQueries" > "calculatingDirtyQueries"
verbose Transition to "runningQueries" > "runningStaticQueries"
verbose Transition to "runningQueries" > "runningPageQueries"
verbose Transition to "runningQueries" > "runningSliceQueries"
verbose Transition to "runningQueries" > "waitingForJobs"
verbose Transition to "runningQueries" > "done"
verbose Transition to "waiting"
info changed file at /Users/treckstar/Code/gatsby/gatsby-apple/src/gatsby-types.d.ts
verbose Transition to "waiting" > "batchingNodeMutations"
verbose Transition to "waiting" > "committingBatch"
verbose Transition to "waiting" > "rebuild"
verbose Transition to "recreatingPages"
verbose Re-Generating schema.graphql
success building schema - 0.086s
verbose Transition to "recreatingPages" > "creatingPages"
verbose Successfully created schema.graphql
success createPages - 0.006s
info Total nodes: 172, SitePage nodes: 13 (use --verbose for breakdown)
verbose Number of node types: 9. Nodes per type: Directory: 25, File: 55, GRVSCCodeBlock: 15, ImageSharp: 6, MarkdownRemark: 5, Site: 1, SiteBuildMetadata: 1, SitePage: 13, SitePlugin: 51
verbose Checking for deleted pages
verbose Deleted 0 pages
verbose Found 0 changed pages
success Checking for changed pages - 0.001s
verbose Transition to "recreatingPages" > "done"
verbose Transition to "runningQueries"
success onPreExtractQueries - 0.001s
verbose Re-Generating fragments.graphql & TS Types
success extract queries from components - 0.063s
verbose Transition to "runningQueries" > "waitingPendingQueries"
verbose Wrote fragments.graphql file to .cache
verbose Transition to "runningQueries" > "writingRequires"
success write out requires - 0.001s
verbose Transition to "runningQueries" > "calculatingDirtyQueries"
verbose Transition to "runningQueries" > "runningStaticQueries"
verbose Transition to "runningQueries" > "runningPageQueries"
verbose Transition to "runningQueries" > "runningSliceQueries"
verbose Transition to "runningQueries" > "waitingForJobs"
verbose Transition to "runningQueries" > "done"
verbose Transition to "waiting"
info changed file at /Users/treckstar/Code/gatsby/gatsby-apple/src/gatsby-types.d.ts
verbose Transition to "waiting" > "batchingNodeMutations"
verbose Transition to "waiting" > "committingBatch"
verbose Transition to "waiting" > "rebuild"
verbose Transition to "recreatingPages"
verbose Re-Generating schema.graphql
success building schema - 0.085s
verbose Transition to "recreatingPages" > "creatingPages"
verbose Successfully created schema.graphql
success createPages - 0.007s
info Total nodes: 172, SitePage nodes: 13 (use --verbose for breakdown)

Also, before the loop happens, and the site opens up the localhost:8000 this message appears:

info Total nodes: 172, SitePage nodes: 13 (use --verbose for breakdown)
verbose Number of node types: 9. Nodes per type: Directory: 25, File: 55, GRVSCCodeBlock: 15, ImageSharp: 6, MarkdownRemark: 5, Site: 1, SiteBuildMetadata: 1, SitePage: 13, SitePlugin: 51
verbose Checking for deleted pages
verbose Deleted 0 pages
verbose Found 0 changed pages
success Checking for changed pages - 0.002s
verbose Transition to "initializingData" > "writingOutRedirects"
success write out redirect data - 0.002s
verbose Transition to "initializingData" > "done"
verbose Transition to "runningPostBootstrap"
success Build manifest and related icons - 0.089s
success onPostBootstrap - 0.094s
info bootstrap finished - 4.107s
verbose Transition to "runningQueries"
success onPreExtractQueries - 0.002s
success extract queries from components - 2.898s
verbose Transition to "runningQueries" > "waitingPendingQueries"
verbose Transition to "runningQueries" > "writingRequires"
success write out requires - 0.005s
verbose Transition to "runningQueries" > "calculatingDirtyQueries"
verbose Transition to "runningQueries" > "runningStaticQueries"
verbose Transition to "runningQueries" > "runningPageQueries"
verbose Transition to "runningQueries" > "runningSliceQueries"
verbose Transition to "runningQueries" > "waitingForJobs"
verbose Transition to "runningQueries" > "done"
verbose Transition to "startingDevServers"

 ERROR  UNKNOWN

Warning: Each child in a list should have a unique "key" prop.

Check the top-level render call using <body>. See https://reactjs.org/link/warning-keys for more information.
    at script
    at HTML (/Users/treckstar/Code/gatsby/gatsby-apple/.cache/page-ssr/routes/render-page.js:3091:96)

verbose Attaching functions to development server
⠀
You can now view gatsby-starter-apple in the browser.
⠀
  http://localhost:8000/
⠀
View GraphiQL, an in-browser IDE, to explore your site's data and schema
⠀
  http://localhost:8000/___graphql
⠀
Note that the development build is not optimized.
To create a production build, use gatsby build

Promptly afterwards, the loop happens.

But like I said, the site is working. Just figured I'd drop this in here. Feel free to close this if this isn't anything to worry about.

Thanks for the great theme!

Add Safari Toolbar color

https://css-tricks.com/safari-15-new-ui-theme-colors-and-a-css-tricks-cameo/

이슈등록

TypeScript Migration

JS to TS + Refactoring

Clone Error

`Cloning into 'gatsby-starter-apple'...
remote: Enumerating objects: 103, done.
remote: Counting objects: 100% (103/103), done.
remote: Compressing objects: 100% (89/89), done.
remote: Total 103 (delta 0), reused 74 (delta 0), pack-reused 0
success Created starter directory layout
info Installing packages...

npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR!
npm ERR! While resolving: [email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/gatsby
npm ERR! gatsby@"^4.5.4" from the root project
npm ERR! peer gatsby@"^4.0.0-next" from [email protected]
npm ERR! node_modules/babel-plugin-remove-graphql-queries
npm ERR! babel-plugin-remove-graphql-queries@"^4.5.2" from [email protected]
npm ERR! babel-plugin-remove-graphql-queries@"^4.4.0" from [email protected]
npm ERR! node_modules/gatsby-plugin-image
npm ERR! gatsby-plugin-image@"^2.4.0" from the root project
npm ERR! 1 more (gatsby-plugin-typescript)
npm ERR! 19 more (gatsby-plugin-alias-imports, gatsby-plugin-feed, ...)
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer gatsby@"^2.12.1 || ^3.1.1" from [email protected]
npm ERR! node_modules/gatsby-remark-vscode
npm ERR! gatsby-remark-vscode@"^3.3.0" from the root project
npm ERR!
npm ERR! Conflicting peer dependency: [email protected]
npm ERR! node_modules/gatsby
npm ERR! peer gatsby@"^2.12.1 || ^3.1.1" from [email protected]
npm ERR! node_modules/gatsby-remark-vscode
npm ERR! gatsby-remark-vscode@"^3.3.0" from the root project
npm ERR!`

Add "overflow-y: auto" to catergory bar style

Currently, the attribute overflow-y: scroll is applied, so unnecessary scroll bars are exposed every time.

Error directly after cloning and running gatsby develop

I've tried cloning numerous times, always get the following error upon attempting gatsby develop

success compile gatsby files - 0.714s

ERROR UNKNOWN

There was a problem loading plugin "gatsby-source-filesystem". Perhaps you need to install its package?
Use --verbose to see actual error.

ERROR UNKNOWN

Failed to resolve gatsby-source-filesystem unreachable

Error: unreachable

• resolve-plugin.ts:95 resolvePlugin
  [jayson.knight]/[gatsby]/src/bootstrap/load-plugins/resolve-plugin.ts:95:11

• index.ts:54 resolveTheme
  [jayson.knight]/[gatsby]/src/bootstrap/load-themes/index.ts:54:42

• index.ts:164
  [jayson.knight]/[gatsby]/src/bootstrap/load-themes/index.ts:164:30

• util.js:16 tryCatcher
  [jayson.knight]/[bluebird]/js/release/util.js:16:23

• reduce.js:166 Object.gotValue
  [jayson.knight]/[bluebird]/js/release/reduce.js:166:18

• reduce.js:155 Object.gotAccum
  [jayson.knight]/[bluebird]/js/release/reduce.js:155:25

• util.js:16 Object.tryCatcher
  [jayson.knight]/[bluebird]/js/release/util.js:16:23

• promise.js:547 Promise._settlePromiseFromHandler
  [jayson.knight]/[bluebird]/js/release/promise.js:547:31

• promise.js:604 Promise._settlePromise
  [jayson.knight]/[bluebird]/js/release/promise.js:604:18

• promise.js:641 Promise._settlePromiseCtx
  [jayson.knight]/[bluebird]/js/release/promise.js:641:10

• async.js:97 _drainQueueStep
  [jayson.knight]/[bluebird]/js/release/async.js:97:12

• async.js:86 _drainQueue
  [jayson.knight]/[bluebird]/js/release/async.js:86:9

• async.js:102 Async._drainQueues
  [jayson.knight]/[bluebird]/js/release/async.js:102:5

• async.js:15 Immediate.Async.drainQueues [as _onImmediate]
  [jayson.knight]/[bluebird]/js/release/async.js:15:14

• timers:475 processImmediate
  node:internal/timers:475:21

not finished load gatsby config - 0.102s

Add Semantic Release

• Commitzen

Build time, deprecated packages

Hi,
the build time is very long on Vercel. More often than not changes are not visible on the website, because the new build failed. Even after redeploying the changes are still not there, which is especially odd, since the old files don't exist anymore in my repo.
I tried to run it locally and npm install took forever as well. It loaded hundreds of deprecated packages.

Create Gatsby Site from starter

I am having many errors for creating a gatsby site from blog starter. There are many errors and I cannot find out what is the cause.
eresolve-report.txt

could someone help me resolve this issues?