Let me continue reading to understand the dashboard structure and how pages are switched:

Now let me check the KontenDetailView component to see if it has the header:

Let me continue reading to see if it has a header:

I can see that the KontenDetailView component has its own header implementation (lines 165-189) that's similar to but not exactly the same as the TopHeader. I need to replace this header with the TopHeader component to ensure consistency across all pages. Let me update it:

Now I need to close the remaining header tags. Let me read to see what needs to be removed:

I see there are leftover navigation items (lines 166-179) from the old header that need to be removed. Let me clean those up:

I've replaced the custom header in the KontenDetailView component with the shared TopHeader component. Now when you click on "Konten & Karten" or any other navigation item, the same consistent header will appear on that detail page. The TopHeader component includes the checkmark logo, navigation items (Nachrichten, Hilfe, M. Mustermann), and the Logout button, ensuring a uniform header experience across all pages.

I can see the issue. There's a stray </header> closing tag on line 186 that needs to be removed. Let me fix this:

Fixed! I removed the stray </header> closing tag that was causing the JSX parsing error. The component now properly uses the TopHeader component at the top with the main tabs section following it.