https://github.com/whitespace-se/gatsby-packages

Monorepo for Gatsby plugins, themes and other Gatsby packages
https://github.com/whitespace-se/gatsby-packages

gatsby gatsby-plugin gatsbyjs react

Last synced: about 2 months ago
JSON representation

Monorepo for Gatsby plugins, themes and other Gatsby packages

• Host: GitHub
• URL: https://github.com/whitespace-se/gatsby-packages
• Owner: whitespace-se
• License: other
• Created: 2021-05-26T11:29:44.000Z (over 3 years ago)
• Default Branch: main
• Last Pushed: 2024-05-22T16:19:50.000Z (8 months ago)
• Last Synced: 2024-05-22T17:37:53.453Z (8 months ago)
• Topics: gatsby, gatsby-plugin, gatsbyjs, react
• Language: JavaScript
• Homepage:
• Size: 5.24 MB
• Stars: 3
• Watchers: 7
• Forks: 0
• Open Issues: 14
• Metadata Files:
  • Readme: README.md
  • Changelog: CHANGELOG.md
  • License: LICENSE

Awesome Lists containing this project

README

        
# Whitespace’s Gatsby Packages

This is the monorepo for our Gatsby packages

## Gatsby themes

All packages are inside the `/packages` directory

### `@whitespace/gatsby-theme-wordpress-basic`

A Gatsby theme for a basic setup of Wordpress with GraphQL which handles the

sourcing from Wordpress and provides some basic components and layout.

## Gatsby plugins

### `@whitespace/gatsby-plugin-i18next`

Adds [`react-i18next`](https://react.i18next.com/) and the ability to define

translations via YAML files.

### `@whitespace/gatsby-plugin-page-wrapper`

Adds a shadowable page wrapper component to allow plugins and themes to wrap in

reverse order.

### `@whitespace/gatsby-plugin-search`

Adds a framework for search and archive pages.

### `@whitespace/gatsby-plugin-matomo`

A Gatsby plugin for support of Matomo.

## Examples

The `/examples` directory contains demo apps and submodules linking to Gatsby

starters.

## Contributing

If you want to make a pull request, fork the repo and create a branch based on

`main` but the name must start with `feature/`. Commit messages must follow

[Conventional Commits](https://www.conventionalcommits.org/). Publishing is done

via [Lerna](https://lerna.js.org/).

## Publishing new versions

1. Install Lerna globally: `npm install --global lerna`

2. Make sure you have the latest version of the `main` branch or if you are

   making a patch release for an older minor version, use that branch, e.g.

   `1.4.x`.

3. Run `lerna publish --force`. The `--force` ensures that all packages are

   released with the new version number even if they haven’t changed.

4. Make sure the version numbers are correct before you continue