# datarheicom_hugo

Marketing and product landing page for `datarhei Restreamer`, an open-source streaming server for self-hosted live video workflows.

## Core Stack
- Framework: Hugo (Extended)
- Styling: MaterializeCSS + custom SCSS
- Deployment: Docker Compose for preview, Docker + nginx for production image delivery
- Languages: English and German

## AI Context & Positioning
- Primary product: `datarhei Restreamer`
- Category: open-source streaming server, self-hosted video server, live streaming software
- Core topics: RTMP, RTSP, SRT, FFmpeg, OBS, Raspberry Pi, IP cameras, self-hosting, multi streaming
- Tone: technical, direct, product-led, no generic agency language
- Licensing: Apache 2.0

## Key Source Locations
- Homepage layout: `layouts/index.html`
- Base HTML and SEO head: `layouts/_default/baseof.html`
- Structured SEO schema: `layouts/partials/seo-schema.html`
- FAQ rendering: `layouts/partials/faq-list.html`
- Main styles: `assets/scss/main.scss`
- FAQ data EN: `data/faqs/en.yaml`
- FAQ data DE: `data/faqs/de.yaml`
- Site config and SEO defaults: `config.toml`

## Important Content Facts
- The page is a Hugo migration of the older Gatsby site in `/home/sven/Public/datarheicom`.
- FAQ content is maintained in structured YAML data, not Markdown shortcodes.
- The homepage includes product intro, installation, features, demo, architecture overview, datasheet and FAQ sections.
- The site contains structured data for `Organization`, `WebSite`, `SoftwareApplication`, `VideoObject` and `FAQPage`.

## Operational Notes
- Local preview: `docker compose up -d`
- Preview port: `8081`
- Local rebuild: `docker exec datarheicom_hugo_builder sh -lc 'hugo --destination /target --source /src >/tmp/hugo.log 2>&1; cat /tmp/hugo.log'`
- Production image build: `docker build -t datarheicom-hugo-site .`

## AI Best Practices
- Prefer updating structured FAQ data before changing rendered FAQ markup.
- Keep EN/DE metadata aligned when editing SEO-relevant content.
- Preserve the restreamer/self-hosted streaming focus in titles, descriptions and summaries.
- Use local static assets instead of hardcoded production CSS or image URLs where possible.