Important note: As I migrated my HP from GatsbyJS to Next.js, this project will not be maintained! But current one absolutely works!

If you're interested in Next.js' version. Check it here: https://github.com/thundermiracle/next-startbootstrap-agency

Why I chose Next.js now: https://thundermiracle.com/blog/en/2022-11-05-migrate-from-gatsbyjs-to-next/

Gatsyby startbootstrap-agency

gatsby version of startbootstrap-agency with i18n supported.

This project is migrated to Gatsby@v4

• check the latest Gatsby@v3 version here.
• check the latest Gatsby@v2 version here.

Preview

Sample page

https://gatsby-startbootstrap-agency.netlify.app

https://gatsbystartbootstrapagency1.gatsbyjs.io/

※ startbootstrap-agency (Original Version)

※ startbootstrap-agency-webpack(Webpack Version)

Note

If you're not interesting in i18n, use StaticQueryVersion instead. StaticQueryVersion gets better performance and better code structure.

How to use

This project is using yarn as the package manager. You have to set yarn as Gatsby-cli's package manager first.

https://www.gatsbyjs.com/docs/glossary/yarn/#using-yarn-as-your-gatsby-package-manager

npm install -g gatsby-cli

gatsby new my-blog-folder https://github.com/thundermiracle/gatsby-startbootstrap-agency

Why Gatsby Version

1. Original version is great but have to load too many unnecessary contents from CDN including all components in bootstrap, all solid & brands icons in fontawesome. That dramatically slows down the FCP(first contentful paint) in 3G environment.

   Using Gatsby could tree-shaking unnecessary code, optimizing images which make first contentful paint very fast.

2. Implementation of i18n in original version is not easy and will make a lot of redundant code.

   i18n is really easy in Gatsby and i18n is more maintainable.

Comparison of Original, Webpack and Gatsby version

Gatsby Version

Webpack Version

Original Version

Basic Configuration

• iconName in Services.md MUST be defined in 'config/CustomIcons.jsx'.

• imageFileName in markdown MUST be added in 'content/assets'.

• all configurable contents are saved in markdown files in 'content' folder.

• change file name's number in 'content/sections' folder to change the sort order.

• nullable items (if defined):

  • anchor in section markdown: display in menu if defined in sections' markdown
  • items in social: twitter, facebook, linkedin, github, medium
  • jumpToAnchor, jumpToAnchorText in Top.md: add button in Top section

i18n Configuration

• set defaultLang in 'config/site.js'

• add langTextMap to 'config/site.js' (LanguageSelector won't display if langTextMap is not defined. Consider using StaticQueryVersion if i18n is not necessary)

• copy markdown files in 'content' folder, rename it to xxxx.[langKey].md and translate the contents

License

This project is licensed under the terms of the MIT license.