Sponsoring Logos

[mtwente]

Pull request

Proposed changes

• add logos of SNF, University of Basel/Department of History, FAG Basel, G&I and Max-Geldner-Stiftung as png file to the index page (not all logos are available as vector graphics)

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.
• I have mentioned all co-authors in the PR description as Co-authored-by: Name <[email protected]>.

Summary by CodeRabbit

• New Features
  • Added a new section under the "Poster" header to acknowledge sponsors, enhancing the document's informational content.
  • Included a logo image featuring various sponsors, improving context and recognition.
• Improvements
  • Enhanced visual separation of content with a horizontal rule and line break for better readability.

[coderabbitai]

Walkthrough

The changes introduce a new section under the "Poster" header in the document, which includes a horizontal rule and a line break for visual separation. It also acknowledges sponsorship for "Digital History Switzerland 2024" with a logo image featuring various sponsors, enhancing the document's informational content.

Changes

Files	Change Summary
index.qmd	Added a new section under "Poster" with a horizontal rule, line break, and sponsorship acknowledgment for "Digital History Switzerland 2024," including a logo image with sponsors.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant Document
    participant Sponsors

    User->>Document: View Poster Section
    Document->>Sponsors: Display Sponsorship Acknowledgment
    Sponsors-->>Document: Show Logo and Sponsor List
    Document-->>User: Render Updated Poster Section

Loading

Poem

🐇
In the meadow where ideas bloom,
A new poster brightens the room.
With sponsors proud, they take their place,
A logo here, a smile on each face.
Let's hop and cheer for changes so grand,
Together we thrive, hand in hand! 🌼

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share

• X
• Mastodon
• Reddit
• LinkedIn

Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[coderabbitai]

Actionable comments posted: 1

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between dc94b7b and 2b9bcad.

Files ignored due to path filters (1)

• images/sponsoring_logos.png is excluded by !**/*.png

Files selected for processing (1)

• index.qmd (1 hunks)

Additional comments not posted (1)

index.qmd (1)

51-52: Good use of HTML elements for visual separation.

The <hr> and <br /> tags are appropriately used to create a clear visual separation between sections.

[coderabbitai]

Actionable comments posted: 0

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 2b9bcad and 7eed842.

Files selected for processing (1)

• index.qmd (1 hunks)

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

• index.qmd