gatsby-packages

Gatsby Source Kontent Plugin

• Fixes #134

Gatsby Kontent Components

• Fixes #163

Fixes:

• #156
• #158

New examples:

• Navigation showcase
• Resolution showcase
• Relationships showcase

Transferred to monorepo (kontent-gatsby-packages) containing two packages + development site:

• @kentico/gatsby-source-kontent
• @kentico/gatsby-kontent-components
• development site @kentico/gatsby-starter-kontent-hello-world

@kentico/gatsby-source-kontent

• Upgrade guide
• Gatsby Cloud support tutorial draft
• feature toggle for taxonomy nodes
• schema definition for taxonomies
• feature toggle for type nodes
• complex error logging

@kentico/gatsby-kontent-components

• Rich text element React component for the component, inline linked item, and images resolution

development site @kentico/gatsby-starter-kontent-hello-world

• Schema extension examples

NPM:

• @kentico/[email protected]
• @kentico/[email protected]
• development site @kentico/gatsby-starter-kontent-hello-world - not published

Fixes:

• #144

Gatsby cloud support:

• How to Tutorial draft

This upgrade is necessary to fix the colliding identifiers issue.

For more info see the upgrade instructions.

Colliding identifiers

It is necessary to rename all Kontent taxonomy, type, and item names in all GraphQL queries.

Accommodate fixed in JS SDK - resolve URLs to HTML

JS SDK upgrade containing issue fix

vNext version

• Gatsby source plugin
  • Upgrade info
• Gatsby Kontent components

This upgrade is necessary to fix colliding identifiers issue.

Colliding identifiers

It is necessary to rename all Kontent taxonomy, type, and item names in all GraphQL queries.

Accommodate fixed in JS SDK - resolve URLs to HTML

JS SDK upgrade containing issue fix

This upgrade is necessary to fix colliding identifiers issue.

Colliding identifiers

It is necessary to rename all Kontent taxonomy, type, and item names in all GraphQL queries.

Accommodate fixed in JS SDK - resolve URLs to HTML

JS SDK upgrade containing issue fix

This upgrade is necessary to fix colliding identifiers issue.

Colliding identifiers

It is necessary to rename all Kontent taxonomy, type, and item names in all GraphQL queries.

• Fix #107
• contentDigest is now computed from raw elements - not the transformed elements for the Gatsby.
• enableLogging configuration option now logs the number of created content item nodes correctly: https://github.com/Kentico/gatsby-source-kontent/commit/0bd36ee605de7afd286675d5244cd0cc4d8d6d7b

Using items-feed instead of items endpoint to prevent getting API limitation response errors

• #101 (#97)

Using items-feed instead of items endpoint to prevent getting API limitation response errors

• #101 (#97)

Thanks to the #79 it is possible to query taxonomies i.e. in case of loading all the taxonomy option to your site.

Version 4.1 was skipped because it was reserved for gatsby preview support (and now v 4.3will be locked for gatsby preview).

New features

Fix schema definition for contentType link

• #95 (#92)
• https://github.com/gatsbyjs/gatsby/pull/20212

Add contentType, contentItems, and usedByContentItems to schema

• #94 (#92)

• Full update support 💪
• all language variant is updated per every call

Issue (https://github.com/gatsbyjs/gatsby/issues/19917) fixed:

• Update fails when editing because the schema is not preserved

15:23:12 PM: error There was an error in your GraphQL query: - Unknown field 'system' on type '[KontentItemHeaderSectionKontentItemTestPreviewKontentItemVideoSectionUnion]'.

• Full update support 💪
• all language variant is updated per every call

Issues:

• Update fails when editing beacuse schema is not preserved

15:23:12 PM: error There was an error in your GraphQL query: - Unknown field 'system' on type '[KontentItemHeaderSectionKontentItemTestPreviewKontentItemVideoSectionUnion]'.

Gatsby preview

• support all 'primitive' elements update handling
  • text
  • number
  • url_slug
  • custom element
  • date & time
• every change is replacing all (supported) elements not just the one lised as edited
  • mainly because url_slug autogeneration -> this field is changed immediately withing the source text element
• removing fields for update run - they are recreated in createNodeField in site logic