diff --git a/.docforge/contribute.yaml b/.docforge/contribute.yaml
new file mode 100644
index 000000000..39115b4ed
--- /dev/null
+++ b/.docforge/contribute.yaml
@@ -0,0 +1,241 @@
+structure:
+ - file: _index.md
+ source: /website/contribute/_index.md
+
+ - dir: contribution-process
+ structure:
+ - fileTree: /website/contribute/contribution-process
+
+ - dir: developer-starter-kit
+ structure:
+ - file: _index.md
+ source: /website/contribute/developer-starter-kit/_index.md
+ - file: local_setup.md
+ frontmatter:
+ weight: 10
+ source: https://github.com/gardener/gardener/blob/master/docs/development/local_setup.md
+ - file: getting_started_locally.md
+ frontmatter:
+ weight: 20
+ source: https://github.com/gardener/gardener/blob/master/docs/deployment/getting_started_locally.md
+ - file: dependencies.md
+ frontmatter:
+ weight: 30
+ source: https://github.com/gardener/gardener/blob/master/docs/development/dependencies.md
+ - file: testing.md
+ frontmatter:
+ weight: 40
+ source: https://github.com/gardener/gardener/blob/master/docs/development/testing.md
+ - file: testmachinery_tests.md
+ frontmatter:
+ weight: 50
+ source: https://github.com/gardener/gardener/blob/master/docs/development/testmachinery_tests.md
+ - file: kubernetes-clients.md
+ frontmatter:
+ weight: 60
+ source: https://github.com/gardener/gardener/blob/master/docs/development/kubernetes-clients.md
+ - file: logging-guidelines.md
+ frontmatter:
+ weight: 70
+ source: https://github.com/gardener/gardener/blob/master/docs/development/logging-guidelines.md
+ - file: changing-the-api.md
+ frontmatter:
+ weight: 80
+ source: https://github.com/gardener/gardener/blob/master/docs/development/changing-the-api.md
+ - file: defaulting.md
+ frontmatter:
+ weight: 90
+ source: https://github.com/gardener/gardener/blob/master/docs/development/defaulting.md
+ - file: validation-guidelines.md
+ frontmatter:
+ weight: 100
+ source: https://github.com/gardener/gardener/blob/master/docs/development/validation-guidelines.md
+
+ - dir: gardener
+ structure:
+ - file: _index.md
+ source: /website/contribute/gardener/_index.md
+ - dir: development
+ structure:
+ - fileTree: https://github.com/gardener/gardener/tree/master/docs/development
+ excludeFiles:
+ - local_setup.md
+ - getting_started_locally.md
+ - testing.md
+ - testmachinery_tests.md
+ - dependencies.md
+ - validation-guidelines.md
+ - ipv6.md
+ - changing-the-api.md
+ - defaulting.md
+ - kubernetes-clients.md
+ - logging-guidelines.md
+ - file: ipv6.md
+ frontmatter:
+ title: IPv6
+ source: https://github.com/gardener/gardener/blob/master/docs/development/ipv6.md
+
+ - dir: extensions
+ structure:
+ - file: _index.md
+ frontmatter:
+ title: Extensions
+ weight: 40
+ - dir: infrastructure-extensions
+ structure:
+ - file: _index.md
+ frontmatter:
+ title: Infrastructure Extensions
+ description: Developer documentation for cloud provider extensions
+ weight: 10
+ - dir: gardener-extension-provider-aws
+ structure:
+ - file: _index.md
+ frontmatter:
+ title: Provider AWS
+ description: Developer documentation for the AWS cloud provider extension
+ source: https://github.com/gardener/gardener-extension-provider-aws/blob/master/README.md
+ - dir: development
+ structure:
+ - fileTree: https://github.com/gardener/gardener-extension-provider-aws/tree/master/docs/development
+ - dir: gardener-extension-provider-gcp
+ structure:
+ - file: _index.md
+ frontmatter:
+ title: Provider GCP
+ description: Developer documentation for the GCP cloud provider extension
+ source: https://github.com/gardener/gardener-extension-provider-gcp/blob/master/README.md
+ - dir: development
+ structure:
+ - fileTree: https://github.com/gardener/gardener-extension-provider-gcp/tree/master/docs/development
+ - dir: gardener-extension-provider-azure
+ structure:
+ - file: _index.md
+ frontmatter:
+ title: Provider Azure
+ description: Developer documentation for the Azure cloud provider extension
+ source: https://github.com/gardener/gardener-extension-provider-azure/blob/master/README.md
+ - dir: development
+ structure:
+ - fileTree: https://github.com/gardener/gardener-extension-provider-azure/tree/master/docs/development
+ - dir: gardener-extension-provider-alicloud
+ structure:
+ - file: _index.md
+ frontmatter:
+ title: Provider Alibaba Cloud
+ description: Developer documentation for the Alibaba Cloud provider extension
+ source: https://github.com/gardener/gardener-extension-provider-alicloud/blob/master/README.md
+ - dir: development
+ structure:
+ - fileTree: https://github.com/gardener/gardener-extension-provider-alicloud/tree/master/docs/development
+ - dir: gardener-extension-provider-openstack
+ structure:
+ - file: _index.md
+ frontmatter:
+ title: Provider OpenStack
+ description: Developer documentation for the OpenStack cloud provider extension
+ source: https://github.com/gardener/gardener-extension-provider-openstack/blob/master/README.md
+ - dir: development
+ structure:
+ - fileTree: https://github.com/gardener/gardener-extension-provider-openstack/tree/master/docs/development
+ - dir: gardener-extension-shoot-dns-service
+ structure:
+ - file: _index.md
+ frontmatter:
+ title: DNS Services
+ description: Developer documentation for the DNS services extension
+ source: https://github.com/gardener/gardener-extension-shoot-dns-service/blob/master/README.md
+ - dir: development
+ structure:
+ - fileTree: https://github.com/gardener/gardener-extension-shoot-dns-service/tree/master/docs/development
+ - dir: gardener-extension-registry-cache
+ structure:
+ - file: _index.md
+ frontmatter:
+ title: Registry Cache
+ description: Developer documentation for the registry cache extension
+ source: https://github.com/gardener/gardener-extension-registry-cache/blob/main/README.md
+ - dir: development
+ structure:
+ - fileTree: https://github.com/gardener/gardener-extension-registry-cache/tree/main/docs/development
+ - dir: gardener-extension-shoot-rsyslog-relp
+ structure:
+ - file: _index.md
+ frontmatter:
+ title: Node Audit Logging
+ description: Developer documentation for the node audit logging extension
+ source: https://github.com/gardener/gardener-extension-shoot-rsyslog-relp/blob/main/README.md
+ - dir: development
+ structure:
+ - fileTree: https://github.com/gardener/gardener-extension-shoot-rsyslog-relp/tree/main/docs/development
+ - dir: gardener-extension-auditing
+ structure:
+ - file: _index.md
+ frontmatter:
+ title: Kubernetes Auditing
+ description: Developer documentation for the Kubernetes auditing extension
+ source: https://github.com/gardener/gardener-extension-auditing/blob/main/README.md
+ - dir: development
+ structure:
+ - fileTree: https://github.com/gardener/gardener-extension-auditing/tree/main/docs/development
+
+ - dir: other-components
+ structure:
+ - file: _index.md
+ frontmatter:
+ title: Other Components
+ weight: 50
+ - dir: machine-controller-manager
+ structure:
+ - file: _index.md
+ frontmatter:
+ title: Machine Controller Manager
+ description: Developer documentation for the machine controller manager
+ source: https://github.com/gardener/machine-controller-manager/blob/master/README.md
+ - dir: development
+ structure:
+ - fileTree: https://github.com/gardener/machine-controller-manager/tree/master/docs/development
+ - dir: etcd-druid
+ structure:
+ - file: _index.md
+ frontmatter:
+ title: etcd-druid
+ description: Developer documentation for the etcd management operator
+ source: https://github.com/gardener/etcd-druid/blob/master/README.md
+ - dir: development
+ structure:
+ - fileTree: https://github.com/gardener/etcd-druid/tree/master/docs/development
+ - dir: dependency-watchdog
+ structure:
+ - file: _index.md
+ frontmatter:
+ title: Dependency Watchdog
+ description: Developer documentation for the dependency watchdog
+ source: https://github.com/gardener/dependency-watchdog/blob/master/README.md
+ - dir: development
+ structure:
+ - fileTree: https://github.com/gardener/dependency-watchdog/tree/master/docs/development
+ excludeFiles:
+ - "setup/"
+ - dir: setup
+ structure:
+ - file: _index.md
+ frontmatter:
+ title: Setup
+ - fileTree: https://github.com/gardener/dependency-watchdog/tree/master/docs/development/setup
+
+ - dir: dashboard
+ structure:
+ - file: _index.md
+ frontmatter:
+ title: Dashboard
+ description: Developer documentation for the Gardener web UI
+ weight: 60
+ source: https://github.com/gardener/dashboard/blob/master/README.md
+ - dir: development
+ structure:
+ - fileTree: https://github.com/gardener/dashboard/tree/master/docs/development
+
+ - dir: documentation
+ structure:
+ - fileTree: /website/contribute/documentation
diff --git a/.docforge/documentation/documentation.yaml b/.docforge/documentation/documentation.yaml
index e2ebf67ad..d35cfdd26 100644
--- a/.docforge/documentation/documentation.yaml
+++ b/.docforge/documentation/documentation.yaml
@@ -42,20 +42,10 @@ structure:
weight: 10
aliases:
- "/api-reference/"
- persona: Developers
source: https://github.com/gardener/gardener/blob/master/docs/api-reference/README.md
- fileTree: https://github.com/gardener/gardener/tree/master/docs/api-reference
excludeFiles:
- "README.md"
- - dir: concepts
- structure:
- - file: _index.md
- frontmatter:
- title: Concepts
- weight: 20
- persona: Operators
- - fileTree: https://github.com/gardener/gardener/tree/master/docs/concepts
- - file: https://github.com/gardener/gardener/blob/master/logo/gardenadm-large.png
- dir: extensions
structure:
- file: _index.md
@@ -63,7 +53,6 @@ structure:
frontmatter:
title: Extensions
weight: 30
- persona: Developers
- dir: resources
structure:
- file: _index.md
@@ -72,6 +61,15 @@ structure:
- fileTree: https://github.com/gardener/gardener/tree/master/docs/extensions
excludeFiles:
- "overview.md"
+ - dir: concepts
+ structure:
+ - file: _index.md
+ frontmatter:
+ title: Concepts
+ weight: 20
+ persona: Operators
+ - fileTree: https://github.com/gardener/gardener/tree/master/docs/concepts
+ - file: https://github.com/gardener/gardener/blob/master/logo/gardenadm-large.png
- dir: deployment
structure:
- file: _index.md
@@ -80,9 +78,6 @@ structure:
weight: 40
persona: Operators
- fileTree: https://github.com/gardener/gardener/tree/master/docs/deployment
- - dir: development
- structure:
- - fileTree: https://github.com/gardener/gardener/tree/master/docs/development
- dir: monitoring
structure:
- file: _index.md
@@ -195,6 +190,7 @@ structure:
- fileTree: https://github.com/gardener/dashboard/tree/master/docs
excludeFiles:
- "README.md"
+ - "development/"
- dir: gardenctl-v2
structure:
- file: _index.md
@@ -226,12 +222,14 @@ structure:
- file: https://github.com/gardener/gardenctl-v2/blob/master/logo/logo_gardener_cli_large.png
- dir: faq
structure:
- - manifest: ./faq.yaml
+ - file: _index.md
+ frontmatter:
+ title: FAQ
+ description: Commonly asked questions about Gardener
+ weight: 80
+ - fileTree: /website/documentation/faq
- file: glossary.md
source: /website/documentation/glossary.md
- dir: resources
structure:
- fileTree: /website/documentation/resources
- - dir: contribute
- structure:
- - fileTree: /website/documentation/contribute
diff --git a/.docforge/documentation/gardener-extensions/infrastructure.yaml b/.docforge/documentation/gardener-extensions/infrastructure.yaml
index af761ed6f..160e3b905 100644
--- a/.docforge/documentation/gardener-extensions/infrastructure.yaml
+++ b/.docforge/documentation/gardener-extensions/infrastructure.yaml
@@ -10,6 +10,7 @@ structure:
excludeFiles:
- "usage/dual-stack-ingress.md" # already included in ../guides.yaml, avoiding duplicates
- "usage/ipv6.md" # already included in ../guides.yaml, avoiding duplicates
+ - "development/"
- dir: gardener-extension-provider-gcp
structure:
- file: _index.md
@@ -21,6 +22,7 @@ structure:
excludeFiles:
- "usage/ipv6.md" # already included in ../guides.yaml, avoiding duplicates
- "proposals/datadisk-image-restore.md" # no added value in including proposals
+ - "development/"
- dir: gardener-extension-provider-azure
structure:
- file: _index.md
@@ -29,6 +31,8 @@ structure:
description: Gardener extension controller for the Azure cloud provider
source: https://github.com/gardener/gardener-extension-provider-azure/blob/master/README.md
- fileTree: https://github.com/gardener/gardener-extension-provider-azure/tree/master/docs
+ excludeFiles:
+ - "development/"
- dir: gardener-extension-provider-alicloud
structure:
- file: _index.md
@@ -37,6 +41,8 @@ structure:
description: Gardener extension controller for the Alibaba cloud provider
source: https://github.com/gardener/gardener-extension-provider-alicloud/blob/master/README.md
- fileTree: https://github.com/gardener/gardener-extension-provider-alicloud/tree/master/docs
+ excludeFiles:
+ - "development/"
- dir: gardener-extension-provider-openstack
structure:
- file: _index.md
@@ -45,6 +51,8 @@ structure:
description: Gardener extension controller for the OpenStack cloud provider
source: https://github.com/gardener/gardener-extension-provider-openstack/blob/master/README.md
- fileTree: https://github.com/gardener/gardener-extension-provider-openstack/tree/master/docs
+ excludeFiles:
+ - "development/"
- dir: gardener-extension-provider-equinix-metal
structure:
- file: _index.md
diff --git a/.docforge/documentation/gardener-extensions/others.yaml b/.docforge/documentation/gardener-extensions/others.yaml
index 0de0ef957..2085a1f35 100644
--- a/.docforge/documentation/gardener-extensions/others.yaml
+++ b/.docforge/documentation/gardener-extensions/others.yaml
@@ -9,6 +9,7 @@ structure:
- fileTree: https://github.com/gardener/gardener-extension-shoot-dns-service/tree/master/docs
excludeFiles:
- "usage/dns_names.md" # already included in ../guides.yaml, avoiding duplicates
+ - "development/"
- dir: gardener-extension-shoot-cert-service
structure:
- file: _index.md
@@ -60,6 +61,8 @@ structure:
description: Gardener extension controller which deploys pull-through caches for container registries.
source: https://github.com/gardener/gardener-extension-registry-cache/blob/main/README.md
- fileTree: https://github.com/gardener/gardener-extension-registry-cache/tree/main/docs
+ excludeFiles:
+ - "development/"
- dir: gardener-extension-shoot-rsyslog-relp
structure:
- file: _index.md
@@ -68,6 +71,8 @@ structure:
description: Gardener extension controller which configures the rsyslog and auditd services installed on shoot nodes.
source: https://github.com/gardener/gardener-extension-shoot-rsyslog-relp/blob/main/README.md
- fileTree: https://github.com/gardener/gardener-extension-shoot-rsyslog-relp/tree/main/docs
+ excludeFiles:
+ - "development/"
- dir: gardener-extension-auditing
structure:
- file: _index.md
@@ -81,6 +86,7 @@ structure:
- operations/event-format.md
- usage/configuration.md
- usage/event-format.md
+ - "development/"
- file: operations-configuration.md
source: https://github.com/gardener/gardener-extension-auditing/blob/main/docs/operations/configuration.md
- file: operations-event-format.md
diff --git a/.docforge/documentation/other-components.yaml b/.docforge/documentation/other-components.yaml
index 5f7b20e79..513234938 100644
--- a/.docforge/documentation/other-components.yaml
+++ b/.docforge/documentation/other-components.yaml
@@ -9,6 +9,8 @@ structure:
description: Declarative way of managing machines for Kubernetes cluster
source: https://github.com/gardener/machine-controller-manager/blob/master/README.md
- fileTree: https://github.com/gardener/machine-controller-manager/tree/master/docs
+ excludeFiles:
+ - "development/"
- dir: etcd-druid
structure:
- file: _index.md
@@ -19,6 +21,7 @@ structure:
- fileTree: https://github.com/gardener/etcd-druid/tree/master/docs
excludeFiles:
- "README.md"
+ - "development/"
- dir: dependency-watchdog
structure:
- file: _index.md
@@ -30,6 +33,7 @@ structure:
- fileTree: https://github.com/gardener/dependency-watchdog/tree/master/docs
excludeFiles:
- "README.md"
+ - "development/"
- dir: gardener-discovery-server
structure:
- file: _index.md
diff --git a/.docforge/website.yaml b/.docforge/website.yaml
index bfc8b9a23..ca3a22ae9 100644
--- a/.docforge/website.yaml
+++ b/.docforge/website.yaml
@@ -13,6 +13,9 @@ structure:
- dir: docs
structure:
- manifest: ./documentation/documentation.yaml
+- dir: contribute
+ structure:
+ - manifest: ./contribute.yaml
- dir: about
structure:
- fileTree: /website/about
diff --git a/.gitignore b/.gitignore
index 8281b795e..5b16f1c11 100755
--- a/.gitignore
+++ b/.gitignore
@@ -10,6 +10,7 @@ hugo/.forestry
hugo/**
!.github/**/*.yaml
+!.docforge/**/*.yaml
content
.vitepress/theme/utils/debug/**
diff --git a/.vitepress/config.mts b/.vitepress/config.mts
index d60953532..0df26bef1 100644
--- a/.vitepress/config.mts
+++ b/.vitepress/config.mts
@@ -2,6 +2,7 @@ import { defineConfig, type SiteConfig } from 'vitepress'
import { fileURLToPath, URL, pathToFileURL } from 'node:url'
import blogSidebar from './theme/blog-sidebar.ts'
import {communitySidebar} from "./theme/community-sidebar.ts";
+import { contributeSidebar } from "./theme/contribute-sidebar.ts";
import path from 'path'
import { SearchResult } from 'minisearch'
import { generateEnhancedDocsSidebar } from './theme/docs-sidebar.ts';
@@ -16,6 +17,7 @@ const siteSrcDir = 'hugo/content'
const allSidebars = {
'/blog/': blogSidebar()['/blog/'],
'/community/': communitySidebar()['/community/'],
+ '/contribute/': contributeSidebar()['/contribute/'],
'/docs/': generateEnhancedDocsSidebar()['/docs/']
};
@@ -129,6 +131,11 @@ function getNavConfig () {
link: '/community',
activeMatch: 'community',
},
+ {
+ text: 'Contribute',
+ link: '/contribute',
+ activeMatch: 'contribute',
+ },
]
}
function getSearchConfig() {
diff --git a/.vitepress/theme/components/CardGrid.vue b/.vitepress/theme/components/CardGrid.vue
new file mode 100644
index 000000000..a4deba665
--- /dev/null
+++ b/.vitepress/theme/components/CardGrid.vue
@@ -0,0 +1,68 @@
+
+
+
+
+
+
+
diff --git a/.vitepress/theme/contribute-sidebar.ts b/.vitepress/theme/contribute-sidebar.ts
new file mode 100644
index 000000000..7c1e3ed69
--- /dev/null
+++ b/.vitepress/theme/contribute-sidebar.ts
@@ -0,0 +1,22 @@
+import { existsSync } from 'node:fs';
+import { join } from 'node:path';
+import { generateWeightSortedSidebar } from './utils/sidebar.ts';
+
+export function contributeSidebar(): any {
+ const contributeDir = join(process.cwd(), 'hugo', 'content', 'contribute');
+
+ if (!existsSync(contributeDir)) {
+ return { '/contribute/': { items: [] } };
+ }
+
+ return generateWeightSortedSidebar({
+ documentRootPath: '/hugo/content',
+ scanStartPath: 'contribute',
+ resolvePath: '/contribute/',
+ collapsed: true,
+ useTitleFromFileHeading: true,
+ useTitleFromFrontmatter: true,
+ useFolderLinkFromIndexFile: true,
+ useFolderTitleFromIndexFile: true,
+ });
+}
diff --git a/.vitepress/theme/index.ts b/.vitepress/theme/index.ts
index 6eb0103d6..c191c6137 100644
--- a/.vitepress/theme/index.ts
+++ b/.vitepress/theme/index.ts
@@ -7,6 +7,8 @@ import VPFooter from './components/VPFooter.vue'
import TaxonomyIndex from './components/TaxonomyIndex.vue'
import Banner from './components/Banner.vue'
import BlogPostMeta from './components/BlogPostMeta.vue'
+import VPFeatures from './components/VPFeatures.vue'
+import CardGrid from './components/CardGrid.vue'
import './style.css'
@@ -22,6 +24,8 @@ export default {
},
enhanceApp({ app }) {
app.component('YouTubeVideo', YouTubeVideo)
+ app.component('VPFeatures', VPFeatures)
+ app.component('CardGrid', CardGrid)
},
} satisfies Theme
diff --git a/.vitepress/theme/style.css b/.vitepress/theme/style.css
index 83d7099c4..5f2026116 100644
--- a/.vitepress/theme/style.css
+++ b/.vitepress/theme/style.css
@@ -1,3 +1,19 @@
+a.action-button {
+ display: inline-block;
+ border-radius: 20px;
+ padding: 8px 20px;
+ font-size: 14px;
+ font-weight: 600;
+ background-color: var(--vp-button-brand-bg);
+ color: var(--vp-button-brand-text) !important;
+ text-decoration: none !important;
+ transition: background-color 0.25s;
+}
+
+a.action-button:hover {
+ background-color: var(--vp-button-brand-hover-bg);
+}
+
:root:where(:lang(fa)) {
--vp-font-family-base:
'Vazirmatn', 'Inter', ui-sans-serif, system-ui, sans-serif,
diff --git a/website/blog/2023/03/03-27-high-availability-and-zone-outage-toleration.md b/website/blog/2023/03/03-27-high-availability-and-zone-outage-toleration.md
index 25964cfe3..001bf5c96 100644
--- a/website/blog/2023/03/03-27-high-availability-and-zone-outage-toleration.md
+++ b/website/blog/2023/03/03-27-high-availability-and-zone-outage-toleration.md
@@ -449,4 +449,4 @@ The Gardener project is Open Source and [hosted on GitHub](https://github.com/ga
Feedback and contributions are always welcome!
-All channels for getting in touch or learning about the project are listed on our [landing page](../../../documentation/contribute/_index.md#community). We are cordially inviting interested parties to join our [bi-weekly meetings](../../../documentation/contribute/_index.md#bi-weekly-meetings).
+All channels for getting in touch or learning about the project are listed on our [landing page](../../../contribute/_index.md#community). We are cordially inviting interested parties to join our [bi-weekly meetings](../../../contribute/_index.md#bi-weekly-meetings).
diff --git a/website/contribute/_index.md b/website/contribute/_index.md
new file mode 100644
index 000000000..c319fe123
--- /dev/null
+++ b/website/contribute/_index.md
@@ -0,0 +1,58 @@
+---
+title: Contribute
+description: Contributor guides for code and documentation
+persona: Developers
+weight: 110
+aside: false
+---
+
+# Welcome to the Contributor page of Gardener
+
+This page is your starting point for contributing to Gardener. It contains all documentation related to developing and documenting Gardener.
+
+We appreciate all kinds of contributions – from fixing a typo to implementing a new feature. Let's grow Gardener together!
+
+## Get Started
+
+
+
+## Contribute to a Specific Area
+
+
diff --git a/website/contribute/contribution-process/_index.md b/website/contribute/contribution-process/_index.md
new file mode 100644
index 000000000..07f91c5bc
--- /dev/null
+++ b/website/contribute/contribution-process/_index.md
@@ -0,0 +1,14 @@
+---
+title: Contribution Process
+url: /contribute/contribution-process/
+persona: Developers
+weight: 10
+---
+
+# Contribution Process
+
+Start here to understand how contributions work, what's required, how reviews happen, and how to take on larger changes.
+
+- [Contributor Guide](./contributor-guide.md): Prerequisites, submission process, and tips for getting your contributions accepted
+- [Community Roles](./roles.md): The different roles within the Gardener community, their tasks and responsibilities
+- [Contributing Bigger Changes](./contributing-bigger-changes.md): Guidelines for scoping and structuring large contributions
\ No newline at end of file
diff --git a/website/documentation/contribute/code/contributing-bigger-changes.md b/website/contribute/contribution-process/contributing-bigger-changes.md
similarity index 99%
rename from website/documentation/contribute/code/contributing-bigger-changes.md
rename to website/contribute/contribution-process/contributing-bigger-changes.md
index b78c67108..eed6db15d 100644
--- a/website/documentation/contribute/code/contributing-bigger-changes.md
+++ b/website/contribute/contribution-process/contributing-bigger-changes.md
@@ -2,7 +2,7 @@
title: Contributing Bigger Changes
sidebar: true
menu: sln
-weight: 60
+weight: 20
---
## Contributing Bigger Changes
diff --git a/website/contribute/contribution-process/contributor-guide.md b/website/contribute/contribution-process/contributor-guide.md
new file mode 100644
index 000000000..c76904a4c
--- /dev/null
+++ b/website/contribute/contribution-process/contributor-guide.md
@@ -0,0 +1,90 @@
+---
+title: Contributor Guide
+persona: Developers
+weight: 10
+---
+
+Thank you for your interest in contributing to Gardener. This page provides an overview of how to get started, what to expect from the contribution process, and how to connect with the community.
+
+## Prerequisites
+
+Before contributing to Gardener, please review and complete the following requirements.
+
+### Code of Conduct
+
+All members of the Gardener community must abide by the
+[Contributor Covenant](https://www.contributor-covenant.org/version/2/1/code_of_conduct/).
+Only by respecting each other can we develop a productive, collaborative community.
+Please report abusive, harassing, or unacceptable behavior to [gardener.opensource@sap.com](mailto:gardener.opensource@sap.com) and/or a Gardener project maintainer.
+
+### Developer Certificate of Origin
+
+Contributors must accept a Developer Certificate of Origin (DCO) before submitting their first pull request. This happens in an automated fashion during the submission process. We use [the standard DCO text of the Linux Foundation](https://developercertificate.org/).
+
+### License
+
+Your contributions to Gardener must be licensed properly:
+
+* Code contributions must be licensed under the [Apache 2.0 License](http://www.apache.org/licenses/LICENSE-2.0)
+* Documentation contributions must be licensed under the [Creative Commons Attribution 4.0 International License](https://creativecommons.org/licenses/by/4.0/legalcode)
+* You need to sign the Contributor License Agreement. We are using *[CLA assistant](https://cla-assistant.io/)*, which provides a click-through workflow for accepting the CLA. For company contributors, the company also needs to sign a corporate license agreement.
+
+## Contributing
+
+Gardener uses GitHub to manage and review pull requests.
+
+* If you are a new contributor, see [Steps to Contribute](#steps-to-contribute).
+* For trivial fixes or improvements, go ahead and create a pull request.
+* For larger, more complex changes, first discuss your ideas
+ on our [mailing list](https://groups.google.com/forum/?fromgroups#!forum/gardener) to avoid unnecessary work and to give you and us a good deal
+ of inspiration.
+* Relevant coding style guidelines are the [Go Code Review
+ Comments](https://github.com/golang/go/wiki/CodeReviewComments)
+ and the _Formatting and style_ section of Peter Bourgon's [Go: Best Practices for Production Environments](http://peter.bourgon.org/go-in-production/#formatting-and-style).
+
+### Steps to Contribute
+
+If you'd like to work on an issue, please claim it first by commenting on the corresponding GitHub issue. This prevents multiple contributors from working on the same issue simultaneously.
+
+If you have questions about an issue, leave a comment in the issue, and one of the maintainers will help you.
+
+Please follow the [Pull Request Checklist](#pull-request-checklist) to ensure a smooth review process.
+
+### Pull Request Checklist
+
+* Branch from `master`. Before submitting your pull request, rebase your changes onto the current `master` branch.
+* Keep commits small and self-contained. Each commit should compile and pass all tests independently.
+* Test your changes thoroughly before you commit them. Preferably, automate your testing with [unit / integration tests](https://github.com/gardener/gardener/blob/master/docs/development/testing.md). If tested manually, describe the test scope in the PR description (e.g., "Test passed: Upgrade K8s version from 1.14.5 to 1.15.2 on AWS, Azure, GCP, Alicloud, OpenStack.").
+* Write a clear and detailed [Pull Request description](../documentation/pr-guidelines.md) to help reviewers understand your changes.
+* Create *Work In Progress [WIP]* pull requests only if you need a clarification or an explicit review before continuing your work.
+* If your patch is not getting reviewed or you need a specific person to review it, you can @mention a reviewer or request a review via our [mailing list](https://groups.google.com/forum/?fromgroups#!forum/gardener).
+* If you add new features, make sure that they are documented in the [Gardener documentation](https://github.com/gardener/documentation).
+* After a review:
+ * If a review requires you to change your commit(s), please test the changes again.
+ * Address each reviewer’s feedback in a separate commit. Do not mix the feedback from multiple reviews in a single commit.
+ * Mark resolved comments as *resolved* in GitHub.
+ * Add a comment to notify reviewers when updates are ready for another review.
+
+### Contributing Bigger Changes
+
+If you want to contribute bigger changes to Gardener, such as when introducing new API resources and their corresponding controllers, or implementing an approved [Gardener Enhancement Proposal](https://github.com/gardener/gardener/tree/master/docs/proposals), follow the guidelines in [Contributing Bigger Changes](./contributing-bigger-changes.md).
+
+### Adding Already Existing Documentation
+
+If you want to add documentation that already exists on GitHub to the website, you should update the central manifest instead of duplicating the content. To find out how to do that, see [Adding Already Existing Documentation](../documentation/adding-existing-documentation.md).
+
+## Issues and Planning
+
+We use GitHub issues to track bugs and enhancement requests. When opening an issue, provide enough details for others to understand and reproduce the problem. You may use the provided issue template, but it is not required.
+
+## Community
+
+### Slack
+
+We use the [Gardener Project workspace](https://gardener-cloud.slack.com) for public communication related to the Gardener project.
+
+### Mailing List
+
+[gardener@googlegroups.com](https://groups.google.com/forum/?fromgroups#!forum/gardener)
+
+The mailing list is hosted on Google Groups. To receive emails, [join the group](https://support.google.com/groups/answer/1067205) as you would any other Google Group.
diff --git a/website/documentation/contribute/code/images/cicd-overview.png b/website/contribute/contribution-process/images/cicd-overview.png
similarity index 100%
rename from website/documentation/contribute/code/images/cicd-overview.png
rename to website/contribute/contribution-process/images/cicd-overview.png
diff --git a/website/documentation/contribute/code/images/cicd-overview.sketch b/website/contribute/contribution-process/images/cicd-overview.sketch
similarity index 100%
rename from website/documentation/contribute/code/images/cicd-overview.sketch
rename to website/contribute/contribution-process/images/cicd-overview.sketch
diff --git a/website/documentation/contribute/code/roles.md b/website/contribute/contribution-process/roles.md
similarity index 99%
rename from website/documentation/contribute/code/roles.md
rename to website/contribute/contribution-process/roles.md
index 52ea70d0f..1a11ca492 100644
--- a/website/documentation/contribute/code/roles.md
+++ b/website/contribute/contribution-process/roles.md
@@ -1,6 +1,6 @@
---
title: Community Roles
-weight: 20
+weight: 30
outline: 2
---
diff --git a/website/contribute/developer-starter-kit/_index.md b/website/contribute/developer-starter-kit/_index.md
new file mode 100644
index 000000000..24ce9aba0
--- /dev/null
+++ b/website/contribute/developer-starter-kit/_index.md
@@ -0,0 +1,20 @@
+---
+title: Developer Starter Kit
+description: Developer documentation for getting started with local Gardener development
+weight: 20
+---
+
+# Developer Starter Kit
+
+This section contains everything you need to start contributing code to Gardener. It walks you through setting up a local development environment and covers the key guidelines and conventions that all Gardener contributors are expected to follow.
+
+- [Local Setup](https://github.com/gardener/gardener/blob/master/docs/development/local_setup.md): How to set up a local Gardener development environment
+- [Deploying Gardener Locally](https://github.com/gardener/gardener/blob/master/docs/deployment/getting_started_locally.md): How to deploy a full Gardener installation on your local machine using kind
+- [Dependency Management](https://github.com/gardener/gardener/blob/master/docs/development/dependencies.md): How to add and manage Go module dependencies in the Gardener project
+- [Testing Strategy and Guidelines](https://github.com/gardener/gardener/blob/master/docs/development/testing.md): The types of tests used in Gardener and the guidelines for writing them
+- [Test Machinery Tests](https://github.com/gardener/gardener/blob/master/docs/development/testmachinery_tests.md): End-to-end tests run against full Gardener installations using Test Machinery
+- [Kubernetes Clients in Gardener](https://github.com/gardener/gardener/blob/master/docs/development/kubernetes-clients.md): Guidelines and best practices for using Kubernetes clients in Gardener components
+- [Logging Guidelines](https://github.com/gardener/gardener/blob/master/docs/development/logging-guidelines.md): Logging conventions and practices used across Gardener components
+- [Changing the API](https://github.com/gardener/gardener/blob/master/docs/development/changing-the-api.md): How to introduce API changes, including the required steps and review process
+- [Defaulting Strategy and Guidelines](https://github.com/gardener/gardener/blob/master/docs/development/defaulting.md): Conventions for writing defaulting functions in Gardener
+- [Validation Guidelines](https://github.com/gardener/gardener/blob/master/docs/development/validation-guidelines.md): Validation practices and conventions used in the Gardener codebase
diff --git a/website/contribute/documentation/_index.md b/website/contribute/documentation/_index.md
new file mode 100644
index 000000000..b35f8e2a9
--- /dev/null
+++ b/website/contribute/documentation/_index.md
@@ -0,0 +1,5 @@
+---
+title: Documentation
+url: /contribute/documentation/
+weight: 70
+---
\ No newline at end of file
diff --git a/website/documentation/contribute/documentation/adding-existing-documentation.md b/website/contribute/documentation/adding-existing-documentation.md
similarity index 100%
rename from website/documentation/contribute/documentation/adding-existing-documentation.md
rename to website/contribute/documentation/adding-existing-documentation.md
diff --git a/website/documentation/contribute/documentation/blog-tags.md b/website/contribute/documentation/blog-tags.md
similarity index 100%
rename from website/documentation/contribute/documentation/blog-tags.md
rename to website/contribute/documentation/blog-tags.md
diff --git a/website/documentation/contribute/documentation/formatting-guide.md b/website/contribute/documentation/formatting-guide.md
similarity index 100%
rename from website/documentation/contribute/documentation/formatting-guide.md
rename to website/contribute/documentation/formatting-guide.md
diff --git a/website/documentation/contribute/documentation/images.md b/website/contribute/documentation/images.md
similarity index 100%
rename from website/documentation/contribute/documentation/images.md
rename to website/contribute/documentation/images.md
diff --git a/website/documentation/contribute/documentation/markup.md b/website/contribute/documentation/markup.md
similarity index 100%
rename from website/documentation/contribute/documentation/markup.md
rename to website/contribute/documentation/markup.md
diff --git a/website/documentation/contribute/documentation/organization.md b/website/contribute/documentation/organization.md
similarity index 100%
rename from website/documentation/contribute/documentation/organization.md
rename to website/contribute/documentation/organization.md
diff --git a/website/documentation/contribute/documentation/pr-guidelines.md b/website/contribute/documentation/pr-guidelines.md
similarity index 100%
rename from website/documentation/contribute/documentation/pr-guidelines.md
rename to website/contribute/documentation/pr-guidelines.md
diff --git a/website/documentation/contribute/documentation/shortcodes.md b/website/contribute/documentation/shortcodes.md
similarity index 100%
rename from website/documentation/contribute/documentation/shortcodes.md
rename to website/contribute/documentation/shortcodes.md
diff --git a/website/documentation/contribute/documentation/style-guide/_index.md b/website/contribute/documentation/style-guide/_index.md
similarity index 100%
rename from website/documentation/contribute/documentation/style-guide/_index.md
rename to website/contribute/documentation/style-guide/_index.md
diff --git a/website/documentation/contribute/documentation/style-guide/concept_template.md b/website/contribute/documentation/style-guide/concept_template.md
similarity index 100%
rename from website/documentation/contribute/documentation/style-guide/concept_template.md
rename to website/contribute/documentation/style-guide/concept_template.md
diff --git a/website/documentation/contribute/documentation/style-guide/reference_template.md b/website/contribute/documentation/style-guide/reference_template.md
similarity index 100%
rename from website/documentation/contribute/documentation/style-guide/reference_template.md
rename to website/contribute/documentation/style-guide/reference_template.md
diff --git a/website/documentation/contribute/documentation/style-guide/task_template.md b/website/contribute/documentation/style-guide/task_template.md
similarity index 100%
rename from website/documentation/contribute/documentation/style-guide/task_template.md
rename to website/contribute/documentation/style-guide/task_template.md
diff --git a/website/contribute/gardener/_index.md b/website/contribute/gardener/_index.md
new file mode 100644
index 000000000..16b61a7a8
--- /dev/null
+++ b/website/contribute/gardener/_index.md
@@ -0,0 +1,27 @@
+---
+title: Gardener
+description: Developer documentation for the Gardener project
+weight: 30
+---
+
+# Gardener
+
+This section contains the developer documentation for core Gardener functionality.
+
+Before diving in, check out the [Developer Starter Kit](../developer-starter-kit/_index.md). There you can learn how to set up your local environment and get familiar with the general development guidelines for Gardener.
+
+- [Releases, Features, Hotfixes](https://github.com/gardener/gardener/blob/master/docs/development/process.md)
+- [Checklist For Adding New Components](https://github.com/gardener/gardener/blob/master/docs/development/component-checklist.md)
+- [High Availability of Deployed Components](https://github.com/gardener/gardener/blob/master/docs/development/high-availability-of-components.md)
+- [Autoscaling Specifics for Components](https://github.com/gardener/gardener/blob/master/docs/development/autoscaling-specifics-for-components.md)
+- [`PriorityClass`es in Gardener Clusters](https://github.com/gardener/gardener/blob/master/docs/development/priority-classes.md)
+- [Secrets Management for Seed and Shoot Cluster](https://github.com/gardener/gardener/blob/master/docs/development/secrets_management.md)
+- [Reversed VPN Tunnel Setup and Configuration](https://github.com/gardener/gardener/blob/master/docs/development/reversed-vpn-tunnel.md)
+- [IPv6 in Gardener Clusters](https://github.com/gardener/gardener/blob/master/docs/development/ipv6.md)
+- [Shoot Advertised Addresses](https://github.com/gardener/gardener/blob/master/docs/development/shoot-advertised-addresses.md)
+- [The Logging Stack in Gardener](https://github.com/gardener/gardener/blob/master/docs/development/logging-stack.md)
+- [Creating Log Parsers for fluent-bit](https://github.com/gardener/gardener/blob/master/docs/development/log_parsers.md)
+- [Adding Support For a New Kubernetes Version](https://github.com/gardener/gardener/blob/master/docs/development/new-kubernetes-version.md)
+- [Removing Support For a Kubernetes Version](https://github.com/gardener/gardener/blob/master/docs/development/remove-support-for-kubernetes-version.md)
+- [Adding a New Cloud Provider](https://github.com/gardener/gardener/blob/master/docs/development/new-cloud-provider.md)
+- [Extending the Monitoring Stack](https://github.com/gardener/gardener/blob/master/docs/development/monitoring-stack.md)
diff --git a/website/documentation/contribute/_index.md b/website/documentation/contribute/_index.md
deleted file mode 100644
index dce21516f..000000000
--- a/website/documentation/contribute/_index.md
+++ /dev/null
@@ -1,116 +0,0 @@
----
-title: Contribute
-description: Contributors guides for code and documentation
-sidebar: true
-menu: sln
-persona: Developers
-weight: 110
----
-
-# Contributing to Gardener
-
-## Welcome
-
-Welcome to the Contributor section of Gardener. Here you can learn how it is possible for you to contribute your ideas and expertise to the project and have it grow even more.
-
-## Prerequisites
-
-Before you begin contributing to Gardener, there are a couple of things you should become familiar with and complete first.
-
-### Code of Conduct
-
-All members of the Gardener community must abide by the
-[Contributor Covenant](https://www.contributor-covenant.org/version/2/1/code_of_conduct/).
-Only by respecting each other can we develop a productive, collaborative community.
-Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting [gardener.opensource@sap.com](mailto:gardener.opensource@sap.com) and/or a Gardener project maintainer.
-
-### Developer Certificate of Origin
-
-Due to legal reasons, contributors will be asked to accept a Developer Certificate of Origin (DCO) before they submit the first pull request to this projects, this happens in an automated fashion during the submission process. We use [the standard DCO text of the Linux Foundation](https://developercertificate.org/).
-
-### License
-
-Your contributions to Gardener must be licensed properly:
-
-* Code contributions must be licensed under the [Apache 2.0 License](http://www.apache.org/licenses/LICENSE-2.0)
-* Documentation contributions must be licensed under the [Creative Commons Attribution 4.0 International License](https://creativecommons.org/licenses/by/4.0/legalcode)
-
-## Contributing
-
-Gardener uses GitHub to manage reviews of pull requests.
-
-* If you are a new contributor see: [Steps to Contribute](#steps-to-contribute)
-
-* If you have a trivial fix or improvement, go ahead and create a pull request.
-
-* If you plan to do something more involved, first discuss your ideas
- on our [mailing list](https://groups.google.com/forum/?fromgroups#!forum/gardener).
- This will avoid unnecessary work and surely give you and us a good deal
- of inspiration.
-
-* Relevant coding style guidelines are the [Go Code Review
- Comments](https://github.com/golang/go/wiki/CodeReviewComments)
- and the _Formatting and style_ section of Peter Bourgon's [Go: Best Practices for Production Environments](http://peter.bourgon.org/go-in-production/#formatting-and-style).
-
-### Steps to Contribute
-
-Should you wish to work on an issue, please claim it first by commenting on the GitHub issue that you want to work on it. This is to prevent duplicated efforts from contributors on the same issue.
-
-If you have questions about one of the issues, with or without the tag, please comment on them and one of the maintainers will clarify it.
-
-We kindly ask you to follow the [Pull Request Checklist](#pull-request-checklist) to ensure reviews can happen accordingly.
-
-### Pull Request Checklist
-
-* Branch from the master branch and, if needed, rebase to the current master branch before submitting your pull request. If it doesn't merge cleanly with master you may be asked to rebase your changes.
-
-* Commits should be as small as possible, while ensuring that each commit is correct independently (i.e., each commit should compile and pass tests).
-
-* Test your changes as thoroughly as possible before your commit them. Preferably, automate your testing with [unit / integration tests](https://github.com/gardener/gardener/blob/master/docs/development/testing.md). If tested manually, provide information about the test scope in the PR description (e.g., “Test passed: Upgrade K8s version from 1.14.5 to 1.15.2 on AWS, Azure, GCP, Alicloud, Openstack.”).
-
-* When creating the PR, follow the [Pull Request Creation Guidelines](./documentation/pr-guidelines.md) to help out the reviewers understand your changes.
-
-* Create *Work In Progress [WIP]* pull requests only if you need a clarification or an explicit review before you can continue your work item.
-
-* If your patch is not getting reviewed or you need a specific person to review it, you can @-reply a reviewer asking for a review in the pull request or a comment, or you can ask for a review on our [mailing list](https://groups.google.com/forum/?fromgroups#!forum/gardener).
-
-* If you add new features, make sure that they are documented in the [Gardener documentation](https://github.com/gardener/documentation).
-
-* If your changes are relevant for operators, consider to update the [ops toolbelt image](https://github.com/gardener/ops-toolbelt).
-
-* Post review:
- * If a review requires you to change your commit(s), please test the changes again.
- * Address the PR review feedback from a reviewer in a separate commit to make it easier for the reviewer to check how their feedback has been addressed. Do not mix PR review feedback from multiple reviews in a single commit. Create a separate commit per a review.
- * Set respective comments in your GitHub review to resolved.
- * Create a general PR comment to notify the reviewers that your amendments are ready for another round of review.
-
-### Contributing Bigger Changes
-
-If you want to contribute bigger changes to Gardener, such as when introducing new API resources and their corresponding controllers, or implementing an approved [Gardener Enhancement Proposal](https://github.com/gardener/gardener/tree/master/docs/proposals), follow the guidelines outlined in [Contributing Bigger Changes](./code/contributing-bigger-changes.md).
-
-### Adding Already Existing Documentation
-
-If you want to add documentation that already exists on GitHub to the website, you should update the central manifest instead of duplicating the content. To find out how to do that, see [Adding Already Existing Documentation](./documentation/adding-existing-documentation.md).
-
-## Issues and Planning
-
-We use GitHub issues to track bugs and enhancement requests. Please provide as much context as possible when you open an issue. The information you provide must be comprehensive enough to reproduce that issue for the assignee. Therefore, contributors may use but aren't restricted to the issue template provided by the Gardener maintainers.
-
-## Community
-
-### Slack
-
-We use the [Gardener Project workspace](https://gardener-cloud.slack.com) for public communication related to the Gardener project.
-Check out the [Community Bio](../../community/_index.md) for an invite link to join the workspace.
-
-Historically, we used the [#gardener](https://kubernetes.slack.com/messages/gardener) channel in the [Kubernetes workspace](http://slack.k8s.io/).
-
-### Mailing List
-
-[gardener@googlegroups.com](https://groups.google.com/forum/?fromgroups#!forum/gardener)
-
-The mailing list is hosted through Google Groups. To receive the lists' emails, [join the group](https://support.google.com/groups/answer/1067205) as you would any other Google Group.
-
-### Other
-
-For additional channels where you can reach us, as well as links to our bi-weekly meetings, visit the [Community page](../../community/_index.md).
diff --git a/website/documentation/contribute/code/_index.md b/website/documentation/contribute/code/_index.md
deleted file mode 100644
index 859730119..000000000
--- a/website/documentation/contribute/code/_index.md
+++ /dev/null
@@ -1,11 +0,0 @@
----
-title: Contributing Code
-url: docs/contribute/code/
-persona: Developers
----
-
-You are welcome to **contribute code** to Gardener in order to fix a bug or to implement a new feature.
-
-The following rules govern code contributions:
-* Contributions must be licensed under the [Apache 2.0 License](http://www.apache.org/licenses/LICENSE-2.0)
-* You need to sign the Contributor License Agreement. We are using *[CLA assistant](https://cla-assistant.io/)* providing a click-through workflow for accepting the CLA. For company contributors additionally the company needs to sign a corporate license agreement. See the following sections for details.
\ No newline at end of file
diff --git a/website/documentation/contribute/code/cicd.md b/website/documentation/contribute/code/cicd.md
deleted file mode 100644
index 132367fa9..000000000
--- a/website/documentation/contribute/code/cicd.md
+++ /dev/null
@@ -1,27 +0,0 @@
----
-title: CI/CD
----
-
-## CI/CD
-
-As an execution environment for CI/CD workloads, we use [Concourse](https://concourse-ci.org).
-We however abstract from the underlying "build executor" and instead offer a
-`Pipeline Definition Contract`, through which components declare their build pipelines as
-required.
-
-
-
-In order to run continuous delivery workloads for all components contributing to the
-[Gardener](https://github.com/gardener) project, we operate a central service.
-
-Typical workloads encompass the execution of tests and builds of a variety of technologies,
-as well as building and publishing container images, typically containing build results.
-
-We are building our CI/CD offering around some principles:
-
-* *container-native* - each workload is executed within a container environment. Components may customise used container images
-* *automation* - pipelines are generated without manual interaction
-* *self-service* - components customise their pipelines by changing their sources
-* *standardisation*
-
-**Learn more on our: [Build Pipeline Reference Manual](https://gardener.github.io/cc-utils/)**
diff --git a/website/documentation/contribute/code/dependencies.md b/website/documentation/contribute/code/dependencies.md
deleted file mode 100644
index 80d2e672b..000000000
--- a/website/documentation/contribute/code/dependencies.md
+++ /dev/null
@@ -1,48 +0,0 @@
----
-title: Dependencies
-remote: https://github.com/gardener/gardener/blob/master/docs/development/testing_and_dependencies.md
----
-## Testing
-
-We follow the BDD-style testing principles and are leveraging the [Ginkgo](https://onsi.github.io/ginkgo/) framework along with [Gomega](http://onsi.github.io/gomega/) as matcher library. In order to execute the existing tests, you can use
-
-```bash
-make test # runs tests
-make verify # runs static code checks and test
-```
-
-There is an additional command for analyzing the code coverage of the tests. Ginkgo will generate standard Golang cover profiles which will be translated into a HTML file by the [Go Cover Tool](https://blog.golang.org/cover). Another command helps you to clean up the filesystem from the temporary cover profile files and the HTML report:
-
-```bash
-make test-cov
-open gardener.coverage.html
-make test-cov-clean
-```
-### sigs.k8s.io/controller-runtime env test
-
-Some of the integration tests in Gardener are using the `sigs.k8s.io/controller-runtime/pkg/envtest` package.
-It sets up a temporary control plane (etcd + kube-apiserver) against the integration tests can run.
-The `test` and `test-cov` rules in the `Makefile` prepare this env test automatically by downloading the respective binaries (if not yet present) and set the necessary environment variables.
-
-You can also run `go test` or `ginkgo` without the `test`/`test-cov` rules.
-In this case you have to set the `KUBEBUILDER_ASSETS` environment variable to the path that contains the etcd + kube-apiserver binaries or you need to have the binaries pre-installed under `/usr/local/kubebuilder/bin`.
-
-## Dependency Management
-
-We are using [go modules](https://github.com/golang/go/wiki/Modules) for depedency management.
-In order to add a new package dependency to the project, you can perform `go get @` or edit the `go.mod` file and append the package along with the version you want to use.
-
-### Updating Dependencies
-
-The `Makefile` contains a rule called `revendor` which performs `go mod vendor` and `go mod tidy`.
-`go mod vendor` resets the main module's vendor directory to include all packages needed to build and test all the main module's packages. It does not include test code for vendored packages.
-`go mod tidy` makes sure `go.mod` matches the source code in the module. It adds any missing modules necessary to build the current module's packages and dependencies, and it removes unused modules that don't provide any relevant packages.
-
-```bash
-make revendor
-```
-
-The dependencies are installed into the `vendor` folder which **should be added** to the VCS.
-
-> [!WARNING]
-> Make sure that you test the code after you have updated the dependencies!
diff --git a/website/documentation/contribute/documentation/_index.md b/website/documentation/contribute/documentation/_index.md
deleted file mode 100644
index 7ce67fd1f..000000000
--- a/website/documentation/contribute/documentation/_index.md
+++ /dev/null
@@ -1,10 +0,0 @@
----
-title: Contributing Documentation
-url: /contribute/docs/
----
-
-You are welcome to **contribute documentation** to Gardener.
-
-The following rules govern documentation contributions:
-* Contributions must be licensed under the [Creative Commons Attribution 4.0 International License](https://creativecommons.org/licenses/by/4.0/legalcode)
-* You need to sign the Contributor License Agreement. We are using *[CLA assistant](https://cla-assistant.io/)* providing a click-through workflow for accepting the CLA. For company contributors additionally the company needs to sign a corporate license agreement. See the following sections for details.