Hinzufügen von Landingpage für CH Ludens Konferenz in 2026

[dk18q074]

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 a new conference listing "Beyond Regional Histories 2026".
  • Published a new conference page with metadata and event details (dates, venue, affiliations, and description).
  • Updated conference content to include banner imagery and external links; noted that further details will follow.

[coderabbitai]

Walkthrough

Adds a new conference entry "Beyond Regional Histories 2026" to the CH Ludens project index and creates a new conference page at content/projects/ch-ludens/Beyond_Regional_Histories/index.qmd; changes are content-only with no executable logic or public API changes.

Changes

Cohort / File(s)	Change Summary
Conference Reference Addition content/projects/ch-ludens/index.qmd	Inserts a new link to "Beyond Regional Histories 2026" and an empty line before the existing Banner.png reference (content-only).
New Conference Page content/projects/ch-ludens/Beyond_Regional_Histories/index.qmd	Adds a new Quarto page with YAML metadata (title, subtitle, date, categories, location, author) and event description, venue, affiliations, and external links (content-only).

Pre-merge checks and finishing touches

❌ Failed checks (2 warnings)

Check name	Status	Explanation	Resolution
Description Check	⚠️ Warning	The pull request description consists entirely of the empty template structure with no content filled in. The "Proposed changes" section contains only a comment placeholder and no actual description of the changes. Additionally, none of the change type checkboxes are selected, and all checklist items remain unchecked. This means the description lacks the critical information required by the template, such as explaining why the changes should be accepted and what type of change is being made.	The author should fill in the "Proposed changes" section with a description of the big picture behind adding the landing page for the CH Ludens conference. Additionally, the appropriate change type checkbox should be selected (likely "New feature" since this adds a new landing page) and relevant checklist items should be checked or explicitly addressed. At minimum, the author should indicate whether they have read the README and whether documentation updates are needed.
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%.	You can run @coderabbitai generate docstrings to improve docstring coverage.

✅ Passed checks (1 passed)

Check name	Status	Explanation
Title Check	✅ Passed	The title "Hinzufügen von Landingpage für CH Ludens Konferenz in 2026" (Adding landing page for CH Ludens conference in 2026) directly corresponds to the main changes in the pull request. The changeset adds a new landing page for the Beyond Regional Histories conference within the CH Ludens project structure and updates the CH Ludens index page with a reference to this new conference. The title is concise, clear, and specific enough to convey the primary change to a teammate reviewing the commit history.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch CHLConf26

---

📜 Recent review details

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 71c8ea4 and 1ab5158.

📒 Files selected for processing (1)

• content/projects/ch-ludens/Beyond_Regional_Histories/index.qmd (1 hunks)

🚧 Files skipped from review as they are similar to previous changes (1)

• content/projects/ch-ludens/Beyond_Regional_Histories/index.qmd

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)

• GitHub Check: Build, Optimize, and Upload Artifacts

---

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.}

[flicksolutions]

looks good to me

[flicksolutions]

sorry i redact my approval :D

there is images missing, broken links and stuff

[coderabbitai]

Actionable comments posted: 1

📜 Review details

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 23a16b2 and 71c8ea4.

📒 Files selected for processing (1)

• content/projects/ch-ludens/Beyond_Regional_Histories/index.qmd (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)

• GitHub Check: Build, Optimize, and Upload Artifacts

🔇 Additional comments (2)

content/projects/ch-ludens/Beyond_Regional_Histories/index.qmd (2)

1-14: LGTM: Well-structured YAML front matter.

The YAML metadata is complete and properly formatted with appropriate title, subtitle, categories, location, and author information including ORCID identifier.

---

20-20: All external links are accessible.

Verification confirmed that all six URLs in the document return HTTP 200 status codes and are functioning correctly.

[flicksolutions]

The AI found a typo and i fixed it. it's ok for me now