Fix and normalize all links in english docs

Author: sdvg

i18n/en/docusaurus-plugin-content-docs/current/03-faq.mdx

@@ -45,16 +45,16 @@ import { KolLink } from '@public-ui/react';
   KoliBri components are not styled solely using embedded CSS or the use of CSS frameworks (such as Bootstrap, Material-UI, Tailwind CSS, etc.), but
   about the technical setting of CSS on the component. This has the advantage that the components are independent of the external CSS. Robustness is an architectural quality objective. It is reflected in the fact that only the component itself decides on its styling.
 - **Why do you need the scheme?**<br/>
-  KoliBri is based on a sophisticated <KolLink _href="/en/docs/concepts/architecture" _label="Architecture" />. For example, the small schema package (@public-ui/schema) is used to define the tag names and language keys of the KoliBri components independently of the concrete implementation. This enables completely detached work with auto-completion when creating the theme, but without needing the components and their dependencies. This has advantages in some integration scenarios, such as static pages or content management systems (CMS).
+  KoliBri is based on a sophisticated <KolLink _label="Architecture" _href="/en/docs/concepts/architecture" />. For example, the small schema package (@public-ui/schema) is used to define the tag names and language keys of the KoliBri components independently of the concrete implementation. This enables completely detached work with auto-completion when creating the theme, but without needing the components and their dependencies. This has advantages in some integration scenarios, such as static pages or content management systems (CMS).
 
 ## Technical
 
 - **Why can KoliBri components really be accessible?**<br/>
   The KoliBri components are designed in terms of software architecture in such a way that they can only be instrumented via properties and not via their own HTML that can be entered. This means that the components can only be controlled via the API (properties). This is a quality feature because the components cannot be manipulated from the outside. The components are very restrictive and can therefore always be accessible.<br/>
-  In order to be able to break out of this restriction, there is the <KolLink _href="/en/docs/concepts/expert-slot" _label="Expert-Slot" />, which makes it possible to embed your own HTML in the component. Accessibility via the expert slot is in the hands of the expert (developer) and should only be used in exceptional cases.
+  In order to be able to break out of this restriction, there is the <KolLink _label="Expert-Slot" _href="/en/docs/concepts/expert-slot" />, which makes it possible to embed your own HTML in the component. Accessibility via the expert slot is in the hands of the expert (developer) and should only be used in exceptional cases.
 - **Why are component properties sometimes named differently from HTML naming?**<br/>
-  In order to keep KoliBri easy to learn, the HTML naming is usually used. But even the HTML standard is not uniform in its naming across several elements (components). And that is why we have chosen uniform names for similar properties in KoliBri. See concept <KolLink _href="/en/docs/concepts/properties" _label="Properties" /> for more information.
+  In order to keep KoliBri easy to learn, the HTML naming is usually used. But even the HTML standard is not uniform in its naming across several elements (components). And that is why we have chosen uniform names for similar properties in KoliBri. See concept <KolLink _label="Properties" _href="/en/docs/concepts/properties" /> for more information.
 
 ## Any questions?
 
-If you still have questions, please send us an email to <KolLink _href="mailto:kolibri@itzbund.de" _label="kolibri@itzbund.de" _icons="codicon codicon-mail" />.
+If you still have questions, please send us an email to <KolLink _label="kolibri@itzbund.de" _href="mailto:kolibri@itzbund.de" _icons="codicon codicon-mail" />.

i18n/en/docusaurus-plugin-content-docs/current/10-get-started/5-frameworks.mdx

@@ -8,7 +8,7 @@ import { KolAlert, KolLink, KolTable } from '@public-ui/react';
 
 ## Installation
 
-All packages/artifacts of KoliBri are provided versioned in the public <kol-link _href="https://www.npmjs.com/search?q=%40public-ui" _target="npmjs">NPM-Registry</kol-link>.
+All packages/artifacts of KoliBri are provided versioned in the public <KolLink _label="NPM-Registry" _href="https://www.npmjs.com/search?q=%40public-ui" _target="_blank" />.
 
 <KolTable
 	_caption="Packages overview"

i18n/en/docusaurus-plugin-content-docs/current/20-concepts/05-styling/35-designer.mdx

@@ -1,28 +1,10 @@
-import {
-	KolAbbr,
-	KolAlert,
-	KolCard,
-	KolHeading,
-	KolIconIcofont,
-	KolIndentedText,
-	KolIcon,
-	KolKolibri,
-	KolDetails,
-	KolLink,
-	KolLogo,
-	KolTable,
-} from '@public-ui/react';
+import {KolCard, KolLink,} from '@public-ui/react';
 
 # Designer
 
 <div className="grid grid-cols-2">
-	<KolCard _headline="Create own theme" _level={2}>
-		<KolLink slot="content" _useCase="nav" _href="/designer" _target="designer">
-			<div className="flex gap-4 py-2">
-				<KolIcon className="homepage" _icons="codicon codicon-paintcan" />
-				<span>Click here to open the designer in a new browser window.</span>
-			</div>
-		</KolLink>
+	<KolCard _label="Create own theme" _level={2}>
+		<KolLink _label="Click here to open the designer in a new browser window." _href="/designer" _target="_blank" _icons={{ left:'codicon codicon-paintcan' }} />
 	</KolCard>
 </div>
 

i18n/en/docusaurus-plugin-content-docs/current/20-concepts/07-swizzling.md

@@ -8,6 +8,8 @@ tags:
   - concept
 ---
 
+import { KolLink } from '@public-ui/react';
+
 ## Motivation
 
 Numerous, sometimes complex requirements for components of design systems or component libraries would not have to be considered over and over again if there were small-scale, easily reusable basic components to carry these requirements.
@@ -24,4 +26,4 @@ The easiest method to customize a KoliBri component is wrapping. Here, an own co
 
 ### Overwriting
 
-Another variant of swizzling is the overwriting of the inner component construction. In Web Components, this is often done using slots. In KoliBri, we have introduced the <kol-link _href="expert-slot" _label="expert slots"></kol-link> for this purpose.
+Another variant of swizzling is the overwriting of the inner component construction. In Web Components, this is often done using slots. In KoliBri, we have introduced the <KolLink _label="expert slots" _href="expert-slot" /> for this purpose.

i18n/en/docusaurus-plugin-content-docs/current/20-concepts/09-formular.mdx

@@ -8,17 +8,17 @@ tags:
   - concept
 ---
 
-As part of the refactoring to improve the developer experience, we have restructured the input components and converted them into separate components according to the <kol-link _href="https://html.spec.whatwg.org/multipage/input.html" _target="w3c">W3C-Aufteilung</kol-link>.
+import { KolLink } from '@public-ui/react';
+
+As part of the refactoring to improve the developer experience, we have restructured the input components and converted them into separate components according to the <KolLink _label="W3C separation" _href="https://html.spec.whatwg.org/multipage/input.html" _target="_blank" />.
 In this way, the respective components only provide the properties that also have a function for the respective type. Properties that were previously maintained but had no function were removed from the programming.
 
 ## Vergleich zum HTML-Tag &lt;input&gt;
 
 <p>
-	If you look at the{' '}
-	<kol-link _href="https://developer.mozilla.org/de/docs/Web/HTML/Element/Input" _target="mozilla">
-		<code>&lt;input&gt;</code>-tag
-	</kol-link>{' '}
-	, then all types of an input field are implemented with only one tag (component). This results in the fact that all properties (attributes/properties) are
+	If you look at the <KolLink _label="" _href="https://developer.mozilla.org/de/docs/Web/HTML/Element/Input" _target="_blank">
+		<span slot="expert"><code>&lt;input&gt;</code>-tag</span>
+	</KolLink>, then all types of an input field are implemented with only one tag (component). This results in the fact that all properties (attributes/properties) are
 	possible, but have no function depending on the type.
 </p>
 

i18n/en/docusaurus-plugin-content-docs/current/20-concepts/10-datenschutz.mdx

@@ -7,14 +7,16 @@ tags:
   - concept
 ---
 
+import { KolLink } from '@public-ui/react';
+
 # Privacy concept
 
 This concept addresses and explains the aspects of the KoliBri component library that are relevant from a data protection perspective.
 
-> The <kol-link _href="/docs_en/datenschutz">privacy policy</kol-link> regarding the open source approach is described in a separate document.
+> The <KolLink _label="privacy policy" _href="/docs_en/datenschutz" /> regarding the open source approach is described in a separate document.
 
 ## Introduction
 
-The component library KoliBri has an obvious and focused target area of its technical functional expression, which is described in detail in the <kol-link _href="/docs_en/manifest">manifest</kol-link>.
+The component library KoliBri has an obvious and focused target area of its technical functional expression, which is described in detail in the <KolLink _label="manifest" _href="/docs_en/manifest" />.
 
 KoliBri is a collection of small, semantically accessible and flexibly reusable web components without any business logic or other data processing functionalities. In particular, it does not contain any functionalities for sending data. The aim is exclusively to ensure semantically accessible HTML markup of the various elements (components) in different style guides.

i18n/en/docusaurus-plugin-content-docs/current/40-project/02-license.mdx

@@ -9,6 +9,8 @@ tags:
   - legal
 ---
 
+import { KolLink } from '@public-ui/react';
+
 # Licensing
 
 ## The EUPL is the "perfect" license‽
@@ -28,10 +30,7 @@ The "European Union Open Source License" (EUPL) is a copyleft license issued by
 
 <kol-alert _type="info">
 	On the website of the European Commission all information about the{' '}
-	<kol-link _href="https://ec.europa.eu/info/european-union-public-licence_en" _target="eupl-1.2">
-		European Union Public Licence (EUPL)
-	</kol-link>{' '}
-	can be found.
+	<KolLink _label="European Union Public Licence (EUPL)" _href="https://ec.europa.eu/info/european-union-public-licence_en" _target="_blank" /> can be found.
 </kol-alert>
 <br />
 <br />

i18n/en/docusaurus-plugin-content-docs/current/41-formular-handling.mdx

@@ -28,7 +28,7 @@ In **KoliBri** the form components are decoupled from the form handling. This ha
 
 ## Input-components
 
-The **input** components are the components that can be used to make form inputs. That means primarily <kol-link _href="/docs/konzepte/formular-input">inputs, select and textarea</kol-link>.
+The **input** components are the components that can be used to make form inputs. That means primarily <KolLink _label="inputs, select and textarea" _href="/docs/konzepte/formular-input" />.
 
 ## Handling adapters
 
@@ -42,7 +42,7 @@ The form handling is then **coupled** with the **input** components via an **ada
 
 ### Lean-Input adapters
 
-For development with TypeScript, **KoliBri** provides the **adapter** component for the form handling library <kol-link _href="https://www.npmjs.com/package/@leanup/form" _label="@leanup/form" _target="npmjs"/>.
+For development with TypeScript, **KoliBri** provides the **adapter** component for the form handling library <KolLink _label="@leanup/form" _href="https://www.npmjs.com/package/@leanup/form" _target="_blank" />.
 
 #### Installation
 

i18n/en/docusaurus-plugin-content-docs/current/99-impressum.mdx

@@ -5,9 +5,9 @@ tags:
   - leagal
 ---
 
-import { KolKolibri, KolLogo } from '@public-ui/react';
-import { KoliBri } from '@site/src/components/KoliBri';
-import { translate } from '@docusaurus/Translate';
+
+import {KolKolibri, KolLink, KolLogo} from '@public-ui/react';
+import {KoliBri} from '@site/src/components/KoliBri';
 
 <div className="flex gap-4">
 	<KolLogo
@@ -31,31 +31,26 @@ import { translate } from '@docusaurus/Translate';
 
 <p>
 	This technical documentation is published by the open source project "<KoliBri />" of the{' '}
-	<kol-link _href="https://itzbund.de" _target="itzbund">
-		Informationstechnikzentrum Bund (ITZBund)
-	</kol-link>
-	.
+	<KolLink _label="Informationstechnikzentrum Bund (ITZBund)" _href="https://itzbund.de" _target="blank" />.
 </p>
 
-### Adress
+### Address
 
 <p>
-	ITZBund Dienstsitz Bonn
-	<br />
-	Bernkasteler Straße 8
-	<br />
-	53175 Bonn
-	<br />
+	ITZBund Dienstsitz Bonn<br />
+	Bernkasteler Straße 8<br />
+	53175 Bonn<br />
 	Germany
 </p>
 
 ### Contact
 
 <p>
-	E-Mail:
-	<kol-link _icons="codicon codicon-mail" _href="mailto:kolibri@itzbund.de" _target="_blank">
-		kolibri@itzbund.de
-	</kol-link>
+	E-Mail: <KolLink
+		_label="kolibri@itzbund.de"
+		_href="mailto:kolibri@itzbund.de"
+		_icons="codicon codicon-mail"
+	/>
 </p>
 
 ### Privacy