kentico / kentico.github.io Goto Github PK

Create type-checking for all Kentico Kontent Field types.

Type checking in react:
https://reactjs.org/docs/typechecking-with-proptypes.html

Basically, it is required to create a set of objects that define a shape of elements in graph model provided by gatsby-source-kentico-cloud plugin.

Requirements:

• text - exact shape
• rich_text - object contains propery walue which is type string
• number - exact shape
• multiple_choice - array of choices - define shape
• date_time - exact shape
• asset - array of asset (define asset type)
• modular_content (Linked items element) - array of objecs
• taxonomy - list of if taxomomy (+ define taxonomy shape)
• url_slug.

Motivation

Make the CSS definition more organized and scalable.

The current state is that most of the CSS is stored in index.scss and the rest is defined inline.

Proposed solution

Extract into separate files:

• Variable definitions
• Mixins
• Global site (page) styles
• Section specific styles and rename the class first, second,... to more semantic ones

After the v2 of package gatsby-source-kentico-cloud is released. Configure the Gatsby to use it.

Requirements:

• Rewrite the query loading data in LandingPage Component according to the Release notes.
  *Adjust sub-components of LandingPage component to expect data according to the changes that were performed in v2.

Brief bug description

Correct copyright to 2019.

Repro steps

1. Go to kentico.github.io
2. See footer

Proposed dolution

Use dynamic counting to not be forced to update it manually every year.

Screenshots

Brief bug description

An issue in Gatsby source plugin could cause indeterministic order of linked items element.

Workaround is implemented in landingPage component.

Expected behavior

Do not need to sort items link linked items element. -> remove the workaround and the section would be in the same order as they are in Kentico Cloud.

Additional context

Wait until the kontent-ai/gatsby-packages#30 is fixed.

Motivation

Project code if full of inline comments disabling of the eslint.
i.e.:
// eslint-disable-next-line no-undef

Proposed solution

Set up es-lint - ideally two different configuration one for frontend and one for Azure functions

Additional context

• https://eslint.org/docs/user-guide/configuring
• kontent-ai/sample-app-react#84
• kontent-ai/sample-app-vue#6
• kontent-ai/sample-app-react#84