Cloned from Gatsby's blog starter and mostly inspired by Dan Abramov's blog.
可以通过 issues 对文章进行评论，欢迎分享您的想法！
The issues labeled by 👋 comments welcome serve as comment section for blog posts, powered by utterances.
To enable the comment section for a blog post, I manually create an issue, take note of the issue id and record it in the corresponding post's front matter with a custom attribute issueId. This could be automated in the future.
Feel free to open new issues for older posts.
I made some custom blocks for layout elements not supported by markdown syntax natively.
The implementation uses remark-custom-blocks and its Gatsby plugin.
Example:
[[tip | 🚨]]
| 作为顶层函数的 coroutine builders 已被废弃，在目前的 API 中相当于通过 `GlobalScope` 开启协程。本文使用 `GlobalScope` 来模拟全局顶层的 coroutine builders。
The whole thing will be wrapped in a <figure> element, while the title portion will end up in a <figcaption>
Example:
[[fig | 黑盒性质：控制流流入 → [黑盒] → 控制流流出，复刻自[njs blog](https://vorpus.org/blog/notes-on-structured-concurrency-or-go-statement-considered-harmful/).]]
| 
| field | description |
|---|---|
hidden: true |
Hide the post from index page. |
book: jcip |
Display book widget with cover and info. See #108. |
Font combination
- heading:
Roboto Slab,Noto Sans SC Black - text:
Noto Serif SC - Code:
JetBrains Mono - blockquote:
Zilla Slab(italic)
Notes
Zilla Slabis a bit too small to mix withNoto Serif SC.Roboto Slabdoes not have italic version.
Start dev server.
gatsby developBuild production files.
gatsby buildCurrently production files are built by and hosted on Vercel.
.
├── src
├── .gitignore
├── .prettierrc
├── gatsby-browser.js
├── gatsby-config.js
├── gatsby-node.js
├── gatsby-ssr.js
├── LICENSE
├── package-lock.json
├── package.json
└── README.md
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.
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.