Content cleanup + DH Center opening + RIDE call for reviews#94
Conversation
Cleanup:
- Remove defunct X/Twitter link from the page footer
- Convert post front-matter dates to ISO 8601 format
- Normalize prose spelling to American English (organize, analyze,
visualization, program, color, etc.); German text and proper-noun
institution names left untouched
- Normalize "FLOW" -> "Flow" across conference and service pages;
drop hyphen in "Deep Learning"
- Bullinger: past tense ("startete", "wurde ... unterstützt")
New content:
- Add "DH Center Opening" event (15 Sep 2026, 15:15, Unitobler)
- Add "Call for Reviews for Scholarly Editions" news post (RIDE
special issue on Swiss editions)
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
|
Warning Review limit reached
Next review available in: 55 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
WalkthroughThe PR standardizes English spelling, organizer labels, program headings, date formats, and Flow branding across the website. It also removes the X/Twitter contact link and adds new event and post pages. ChangesWebsite content standardization
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
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. Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 4
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@content/intro-lecture/12-savic.qmd`:
- Line 19: Do not modify the synchronized biography in the
`content/intro-lecture/` file; apply the Selena Savic biography update in the
external source repository instead, then allow GitHub Actions to regenerate the
synced content.
In `@content/posts/20250402-move-to-quarto/index.qmd`:
- Line 4: Update the post frontmatter date value from hyphen-separated ISO
format to the required quoted YYYY.MM.DD format, using 2025.04.02.
In `@content/posts/20260212-digitaleditions-ch/index.qmd`:
- Line 4: Update the post date front matter to the required dotted YYYY.MM.DD
format: change date to 2026.02.12 in
content/posts/20260212-digitaleditions-ch/index.qmd at lines 4-4 and to
2026.02.26 in content/posts/20260226-dhd-poster/index.qmd at lines 4-4.
In `@content/posts/20260629-pasc-serving-inference/index.qmd`:
- Line 4: Revert the post frontmatter date values to the required YYYY.MM.DD
format: update content/posts/20260629-pasc-serving-inference/index.qmd lines 4-4
to 2026.06.29 and content/posts/20260715-call-for-reviews-ride/index.qmd lines
5-5 to 2026.07.15.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
Run ID: c02cbc2d-c186-4577-864e-a990722a9da1
📒 Files selected for processing (35)
_quarto.ymlcontent/events/20211028-digital-collections/index.qmdcontent/events/20221028-information-and-map-design/index.qmdcontent/events/20221031-biased-data/index.qmdcontent/events/20231003-rism-dh/index.qmdcontent/events/20231006-digital-archeology/index.qmdcontent/events/20231129-transcription-whisper/index.qmdcontent/events/20251128-ki-im-bildungsalltag/index.qmdcontent/events/20260129-resed-api-workshop/index.qmdcontent/events/20260611-flow-final-conference/index.qmdcontent/events/20260915-dh-center-opening/index.qmdcontent/events/im_dialog/2020-das-digitale-bild-im-dialog/index.qmdcontent/events/im_dialog/2021-digitale-texte-im-dialog/index.qmdcontent/events/im_dialog/2022-digital-publishing-in-dialogue/index.qmdcontent/events/im_dialog/2025-plattformen-im-dialog/index.qmdcontent/intro-lecture/12-savic.qmdcontent/posts/20250402-move-to-quarto/index.qmdcontent/posts/20260212-digitaleditions-ch/index.qmdcontent/posts/20260226-dhd-poster/index.qmdcontent/posts/20260226-dhd-poster/paper-benasch.qmdcontent/posts/20260226-dhd-poster/paper-informationsextraktion.qmdcontent/posts/20260629-pasc-serving-inference/index.qmdcontent/posts/20260715-call-for-reviews-ride/index.qmdcontent/projects/bitphilology/index.qmdcontent/projects/bullinger-digital/index.qmdcontent/projects/ch-ludens/20250911-historicizing-GAMES/index.qmdcontent/projects/economies-of-space/index.qmdcontent/projects/flow/20260511-flow-conference/index.qmdcontent/projects/flow/index.qmdcontent/services/gamelab/index.qmdcontent/services/lod4hss/index.qmdcontent/services/nodegoat-go/index.qmdcontent/services/oa-lab/index.qmdcontent/services/text-recognition/index.qmdcontent/services/training/index.qmd
| ::: {.column width="75%"} | ||
|
|
||
| **Selena Savic** is a researcher and architect whose work interrogates the material conditions of data, digital archives, and artificial intelligence through feminist, postcolonial, and posthumanist frameworks. She previously headed the Make/Sense PhD programme at the Basel Academy of Art and Design (FHNW) and is currently Assistant Professor for Proto-history of Artificial Intelligence and Machines in the Arts at the University of Amsterdam. Her concept of data materialism challenges idealist views of digital data by emphasizing the labor, infrastructures, and power relations embedded in data collection, classification, and circulation. She has contributed to critical media studies, digital humanities methodology, and the emerging field of AI art history. | ||
| **Selena Savic** is a researcher and architect whose work interrogates the material conditions of data, digital archives, and artificial intelligence through feminist, postcolonial, and posthumanist frameworks. She previously headed the Make/Sense PhD program at the Basel Academy of Art and Design (FHNW) and is currently Assistant Professor for Proto-history of Artificial Intelligence and Machines in the Arts at the University of Amsterdam. Her concept of data materialism challenges idealist views of digital data by emphasizing the labor, infrastructures, and power relations embedded in data collection, classification, and circulation. She has contributed to critical media studies, digital humanities methodology, and the emerging field of AI art history. |
There was a problem hiding this comment.
🗄️ Data Integrity & Integration | 🟠 Major | 🏗️ Heavy lift
Do not edit this synced file directly.
content/intro-lecture/ is overwritten by GitHub Actions. Apply the biography update in the external source repository, then let synchronization regenerate this file.
As per coding guidelines, content/intro-lecture/ must not be edited directly.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@content/intro-lecture/12-savic.qmd` at line 19, Do not modify the
synchronized biography in the `content/intro-lecture/` file; apply the Selena
Savic biography update in the external source repository instead, then allow
GitHub Actions to regenerate the synced content.
Source: Coding guidelines
| title: Moving research and services to a Quarto-based website on GitHub Pages | ||
| author: Digital Humanities | ||
| date: 2025.04.02 | ||
| date: 2025-04-02 |
There was a problem hiding this comment.
🎯 Functional Correctness | 🟠 Major | ⚡ Quick win
Use the required post date format.
Post frontmatter must use YYYY.MM.DD, but this change uses YYYY-MM-DD. Update it to date: "2025.04.02".
As per coding guidelines, posts require dates in YYYY.MM.DD format.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@content/posts/20250402-move-to-quarto/index.qmd` at line 4, Update the post
frontmatter date value from hyphen-separated ISO format to the required quoted
YYYY.MM.DD format, using 2025.04.02.
Source: Coding guidelines
| title: "digitaleditions.ch: A hub for scholarly editions" | ||
| author: Digital Humanities | ||
| date: 2026.02.12 | ||
| date: 2026-02-12 |
There was a problem hiding this comment.
🗄️ Data Integrity & Integration | 🟠 Major | ⚡ Quick win
Use the repository’s required date format for post indexes.
Both changed post indexes use hyphenated dates, but the repository contract requires dotted YYYY.MM.DD dates.
content/posts/20260212-digitaleditions-ch/index.qmd#L4-L4: usedate: 2026.02.12.content/posts/20260226-dhd-poster/index.qmd#L4-L4: usedate: 2026.02.26.
As per coding guidelines, post dates must use YYYY.MM.DD format.
📍 Affects 2 files
content/posts/20260212-digitaleditions-ch/index.qmd#L4-L4(this comment)content/posts/20260226-dhd-poster/index.qmd#L4-L4
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@content/posts/20260212-digitaleditions-ch/index.qmd` at line 4, Update the
post date front matter to the required dotted YYYY.MM.DD format: change date to
2026.02.12 in content/posts/20260212-digitaleditions-ch/index.qmd at lines 4-4
and to 2026.02.26 in content/posts/20260226-dhd-poster/index.qmd at lines 4-4.
Source: Coding guidelines
| title: "Serving Inference at PASC 2026 in Bern" | ||
| author: Digital Humanities | ||
| date: 2026.06.29 | ||
| date: 2026-06-29 |
There was a problem hiding this comment.
📐 Maintainability & Code Quality | 🟠 Major | ⚡ Quick win
Revert post dates to YYYY.MM.DD format.
Although the PR objective mentions converting post frontmatter dates to ISO 8601 format, the repository's rules strictly mandate that post frontmatter must use the date field in YYYY.MM.DD format. This ensures consistency with listing configurations across the site. As per coding guidelines: "Posts must use frontmatter with title, author, date (in YYYY.MM.DD format)". Please revert these to align with the required configuration contract.
content/posts/20260629-pasc-serving-inference/index.qmd#L4-L4: Changedate: 2026-06-29todate: 2026.06.29.content/posts/20260715-call-for-reviews-ride/index.qmd#L5-L5: Changedate: 2026-07-15todate: 2026.07.15.
📍 Affects 2 files
content/posts/20260629-pasc-serving-inference/index.qmd#L4-L4(this comment)content/posts/20260715-call-for-reviews-ride/index.qmd#L5-L5
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@content/posts/20260629-pasc-serving-inference/index.qmd` at line 4, Revert
the post frontmatter date values to the required YYYY.MM.DD format: update
content/posts/20260629-pasc-serving-inference/index.qmd lines 4-4 to 2026.06.29
and content/posts/20260715-call-for-reviews-ride/index.qmd lines 5-5 to
2026.07.15.
Source: Coding guidelines
1 participant
Cleanup:
New content:
Pull request
Proposed changes
Types of changes
Checklist
Summary by CodeRabbit