add dhd and poster info

[thodel]

Pull request

Proposed changes

Types of changes

• New feature (non-breaking change which adds functionality).
• Enhancement (non-breaking change which enhances functionality)
• Bug Fix (non-breaking change which fixes an issue).
• Breaking change (fix or feature that would cause existing functionality to change).

Checklist

• I have read the README document.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.

Summary by CodeRabbit

• Documentation
  • Added comprehensive DHD 2026 Vienna poster materials: two German scholarly papers covering an annotation schema and an information-extraction workflow, with methods, results, bibliographies and footnotes.
• New Features
  • Poster previews with linked images and expandable callouts providing full-paper metadata and author details.
• Other
  • Extended introductions, methodology (layout/segmentation, OCR/ATR, extraction, validation) and practical outlook.
• Chores
  • Minor README markup spacing adjustment.

[coderabbitai]

Warning

Rate limit exceeded

@thodel has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 12 minutes and 53 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

📥 Commits

Reviewing files that changed from the base of the PR and between 1dfa5ee and 836bd97.

📒 Files selected for processing (1)

• content/posts/20260226-dhd-poster/index.qmd

Walkthrough

Adds three German Quarto posts for the DHD 2026 Vienna poster: an index overview and two full-paper QMDs (information extraction; BeNASch annotation). Total ~324 lines added. Content-only changes (front matter, authors, sections, figures, bibliographies); no executable code or API changes.

Changes

Cohort / File(s)	Summary
DHD 2026 Vienna Poster — overview & papers content/posts/20260226-dhd-poster/index.qmd, content/posts/20260226-dhd-poster/paper-benasch.qmd, content/posts/20260226-dhd-poster/paper-informationsextraktion.qmd	Adds an overview post and two German QMD papers. Includes YAML front matter, author metadata, narratives (intro, methods, results, outlook), poster previews, expandable callouts linking full papers, figures/references, bibliographies, and footnotes. Content-only; no code or public API changes.
Repository README README.md	Minor markup indentation change in two <summary> tags. No semantic or functional change.

🚥 Pre-merge checks | ✅ 1 | ❌ 2

❌ Failed checks (2 inconclusive)

Check name	Status	Explanation	Resolution
Title check	❓ Inconclusive	The title 'add dhd and poster info' is vague and generic, using non-descriptive terms that don't clearly convey what DHD or poster changes are being made.	Use a more descriptive title that specifies the content being added, such as 'Add DHD 2026 Vienna poster content with paper summaries' or 'Add poster presentations for UNIBE DHD conference'.
Description check	❓ Inconclusive	The PR description follows the template structure but lacks the critical 'Proposed changes' section, leaving the main purpose unexplained despite checking the 'new feature' box.	Fill in the 'Proposed changes' section with details about adding DHD poster content, including context about the UNIBE conference and the two papers being presented.

✅ Passed checks (1 passed)

Check name	Status	Explanation
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@content/posts/20260226-dhd-poster/index.qmd`:
- Around line 7-8: The YAML frontmatter's categories field is malformed: it
mixes a scalar value ("Post") with a list item; update the categories entry in
index.qmd to be a proper YAML sequence either by converting to block-list form
(e.g., replace the scalar and following line with a dash-prefixed list: -
conference, - poster, - Post) or by using an inline array (e.g., categories:
["conference","poster","Post"]); ensure the field header is a single key named
categories and contains only one valid YAML list.

---

ℹ️ Review info

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 305bbd8 and e9a9009.

⛔ Files ignored due to path filters (2)

• content/posts/20260226-dhd-poster/Poster_Wien_Sterbedaten.png is excluded by !**/*.png
• content/posts/20260226-dhd-poster/dhd2026_Poster_Wien_Sterbedaten_preview.png is excluded by !**/*.png

📒 Files selected for processing (3)

• content/posts/20260226-dhd-poster/index.qmd
• content/posts/20260226-dhd-poster/paper-benasch.qmd
• content/posts/20260226-dhd-poster/paper-informationsextraktion.qmd

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@README.md`:
- Line 134: The README line with the HTML summary tag ("<summary>👩‍💻 Setup
Locally (Advanced Users)</summary>") has incorrect indentation/formatting that
fails Prettier; fix the formatting for that summary tag (restore the intended
indentation or surrounding markdown structure) and then run the formatter (npm
run format or prettier --write README.md) to ensure the file passes Prettier
checks before merging.

---

ℹ️ Review info

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 48b9eb6 and 1dfa5ee.

📒 Files selected for processing (1)

• README.md

[coderabbitai]

⚠️ Potential issue | 🟡 Minor

Fix formatting to pass Prettier checks.

The indentation change on this line introduced formatting inconsistencies that fail the Prettier check. The pipeline failure indicates this must be corrected before merge.

Run the following command to auto-fix formatting issues:

npm run format

Or directly:

prettier --write README.md

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@README.md` at line 134, The README line with the HTML summary tag
("<summary>👩‍💻 Setup Locally (Advanced Users)</summary>") has incorrect
indentation/formatting that fails Prettier; fix the formatting for that summary
tag (restore the intended indentation or surrounding markdown structure) and
then run the formatter (npm run format or prettier --write README.md) to ensure
the file passes Prettier checks before merging.