diff --git a/packages/dnb-design-system-portal/src/docs/contribute.mdx b/packages/dnb-design-system-portal/src/docs/contribute.mdx index 798650d66d7..c5a2d38ff87 100644 --- a/packages/dnb-design-system-portal/src/docs/contribute.mdx +++ b/packages/dnb-design-system-portal/src/docs/contribute.mdx @@ -5,7 +5,11 @@ description: 'Project overview, development guides, conventions etc.' import { Button } from '@dnb/eufemia/src' import Card from 'dnb-design-system-portal/src/shared/menu/Card' -import { NewContributor, GettingStarted, Principles } from 'Docs/contribute/assets/graphics' +import { + NewContributor, + GettingStarted, + Principles, +} from 'Docs/contribute/assets/graphics' # Contributing to Eufemia diff --git a/packages/dnb-design-system-portal/src/docs/contribute/contact.mdx b/packages/dnb-design-system-portal/src/docs/contribute/contact.mdx index 9127d9726e4..a947b430089 100644 --- a/packages/dnb-design-system-portal/src/docs/contribute/contact.mdx +++ b/packages/dnb-design-system-portal/src/docs/contribute/contact.mdx @@ -12,7 +12,9 @@ import { Button } from '@dnb/eufemia/src' For all discussion topics, ask in Slack: - + ### Related channels in [DNB IT](https://dnb-it.slack.com) diff --git a/packages/dnb-design-system-portal/src/docs/contribute/first-contribution.mdx b/packages/dnb-design-system-portal/src/docs/contribute/first-contribution.mdx index 004e000719d..8cc4abddd09 100644 --- a/packages/dnb-design-system-portal/src/docs/contribute/first-contribution.mdx +++ b/packages/dnb-design-system-portal/src/docs/contribute/first-contribution.mdx @@ -13,7 +13,13 @@ import { Button, Blockquote, Section } from '@dnb/eufemia/src' If you are new to the Eufemia Library, we would recommend following an intro to the elementary parts of Eufemia.
-
## Your first contribution @@ -44,7 +50,13 @@ More information in [Style guides - Git convention](/contribute/style-guides/git Have a look at the "before getting started" section for a description of technical details. In this section, you will find what packages are included, design decisions explained, the format of the component structure, what purpose different files have, what happens during a build, and the different development environments.
-
## What to expect from the maintainers @@ -56,8 +68,18 @@ As of this date, there are only a few maintainers. That means you can expect **l ## Next step
-The best way to understand a project is to just jump on a real task. It is scary, but the easiest and quickest way of getting into a new project. Also, you should not be afraid of having an imperfect commit, that's really what pull requests are for! -Dina, new contributor + The best way to understand a project is to just jump on a real task. It + is scary, but the easiest and quickest way of getting into a new project. + Also, you should not be afraid of having an imperfect commit, that's + really what pull requests are for! + Dina, new contributor
-