Datenschutz und Impressum MD's hinzugefügt und calls angepasst.

[Hellocrafting]

No description provided.

[Copilot]

Pull request overview

This PR adds legal Markdown documents (Datenschutzerklärung + Impressum) to the frontend and wires up navigation links to them from the homepage header.

Changes:

• Added Datenschutz.md with a full privacy policy text.
• Added Impressum.md with imprint/contact information.
• Replaced placeholder homepage links with anchors pointing to the new Markdown files.

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 7 comments.

File	Description
project/frontend/app/homepage/MarkdownFiles/Impressum.md	New Impressum Markdown document.
project/frontend/app/homepage/MarkdownFiles/Datenschutz.md	New Datenschutzerklärung Markdown document.
project/frontend/app/homepage/homepage.tsx	Adds header links intended to reach the new legal documents.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[Copilot]

Pull request overview

Copilot reviewed 7 out of 7 changed files in this pull request and generated 4 comments.

Comments suppressed due to low confidence (3)

project/frontend/app/components/markdown-renderer.tsx:43

• The code renderer likely receives non-DOM props from react-markdown (commonly inline, node, and sometimes className for fenced code blocks). Spreading them onto <code> can produce invalid attributes and also prevents distinguishing inline vs block code. Consider destructuring inline/node (and handling className/language) instead of blindly spreading.

    code: (props: ComponentPropsWithoutRef<"code">) => (
        <code className="rounded bg-gray-100 px-1.5 py-0.5 font-mono text-sm text-gray-800" {...props} />
    ),

project/frontend/app/datenschutz/page.tsx:28

• This page renders its own <h1> and the markdown file also starts with a # ... heading, which will result in multiple H1s and duplicated titles (accessibility/SEO). Either remove the page-level heading and rely on the markdown heading, or adjust the renderer/markdown so the top-level markdown heading is demoted to h2.

        <main className="min-h-screen bg-white px-6 py-12">
            <div className="mx-auto max-w-4xl">
                <h1 className="text-3xl font-semibold mb-6">Datenschutzerklärung</h1>
                <p className="text-gray-600 mb-8">
                    Die vollständige Datenschutzerklärung wird hier aus der bestehenden Markdown-Datei angezeigt.
                </p>
                <MarkdownRenderer content={content} />
            </div>

project/frontend/app/impressum/page.tsx:28

• This page renders its own <h1> and the markdown file also starts with a # ... heading, which will result in multiple H1s and duplicated titles (accessibility/SEO). Either remove the page-level heading and rely on the markdown heading, or adjust the renderer/markdown so the top-level markdown heading is demoted to h2.

        <main className="min-h-screen bg-white px-6 py-12">
            <div className="mx-auto max-w-4xl">
                <h1 className="text-3xl font-semibold mb-6">Impressum</h1>
                <p className="text-gray-600 mb-8">
                    Das vollständige Impressum wird hier aus der bestehenden Markdown-Datei angezeigt.
                </p>
                <MarkdownRenderer content={content} />
            </div>

[Copilot]

Implemented in 9a07002: extracted the duplicated readMarkdownFile into app/lib/read-markdown.ts and switched /datenschutz and /impressum pages to use the shared helper.