# Goal

Prepare a working public layer for the new version of the website where all migrated content has proper representation and stable routes.

## What to do

- Implement templates for the main page types identified during the inventory.
- Set up routes for sections, lists, material cards, and service pages.
- Restore main navigation, hierarchy, breadcrumbs, and internal linking.
- Ensure consistent behavior for titles, metadata, images, and related materials.
- Handle empty states, missing entities, and 404s.
- Verify responsiveness and basic accessibility for key templates.
- Coordinate routes with the URL preservation and redirection task.

## Result

A set of working haih-cms templates and routes sufficient to display all core public content.

## Definition of Done

- All key page types open successfully in the new implementation.
- Navigation and links between materials work properly.
- URLs are generated predictably and match the migration map.
- Error and missing routes are handled correctly.
- Pages are ready for further SEO and content testing.

Implement the core page templates, navigation, and routing in haih-cms required to replace the Ruby-based website.

Prepare haih-cms templates and routes

## Adjusting the Public Layer Architecture

After deciding to unify the content data around `Concept`, the rendering task is also simplified: there is no longer a need to automatically reproduce a separate template for each legacy entity type. The universal Concept renderer should become the baseline, and specialized views should only be added when there is a real user need.

This reduces the amount of code that needs to be maintained and allows AI-generated/AI-updated content to be published through a common mechanism.

Worklog for task "Prepare haih-cms templates and routes"

Adjusting the Public Layer Architecture

Task: Prepare haih-cms templates and routes