feat(tournaments): add ghc infos

[Noelierx]

In progress, do not merge.

Summary by CodeRabbit

• New Features
  • Introduced a new "Game'Her Challenge" section in the tournaments view, featuring a toggle button for additional information.
  • Added new visual elements and statistics related to the challenge, enhancing user engagement.
• Style
  • Implemented new CSS classes to improve styling and layout for the Game'Her Challenge component, including background image and responsive design elements.

[coderabbitai]

Walkthrough

This update introduces a vibrant "Game'Her Challenge" section to enhance user engagement in the application. With new CSS classes for styling and a structured layout in the HTML template, users can now enjoy a visually appealing interface featuring branding, statistics, and interactive elements. These changes aim to elevate the overall user experience without altering existing functionality.

Changes

Files	Change Summary
assets/css/tournament.css	Added new CSS classes for the Game'Her Challenge, including .gameherChallenge, .gameherChallenge__trigger, .gameherChallenge__kpi, and .gameherChallenge__button, enhancing styling and layout.
templates/views/tournaments.html.twig	Introduced a "Game'Her Challenge" section with a title, toggle button, branding, and statistics, improving interactivity and responsiveness.

Poem

🐰 In a world of games, bright and bold,
A challenge awaits, new stories unfold.
With colors and stats, our hearts take flight,
Join the Game'Her Challenge, it feels just right!
Hop along with joy, in the fun we partake,
Together we'll strive, for each victory we make! 🎉

---

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

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

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: 0

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 6ed4750 and 0a9b857.

Files ignored due to path filters (8)

• assets/img/tournaments/GHChallenge/background-ghc.png is excluded by !**/*.png
• assets/img/tournaments/GHChallenge/logo.png is excluded by !**/*.png
• assets/img/tournaments/GHChallenge/matchs.png is excluded by !**/*.png
• assets/img/tournaments/GHChallenge/players.png is excluded by !**/*.png
• assets/img/tournaments/GHChallenge/podium.png is excluded by !**/*.png
• assets/img/tournaments/GHChallenge/teams.png is excluded by !**/*.png
• composer.lock is excluded by !**/*.lock
• symfony.lock is excluded by !**/*.lock

Files selected for processing (2)

• assets/css/tournament.css (4 hunks)
• templates/views/tournaments.html.twig (1 hunks)

Additional comments not posted (5)

assets/css/tournament.css (4)

10-17: Consistent styling for .gameherChallenge.

The styling is consistent with .gameherLeague, maintaining visual coherence across sections.

---

37-41: Correct implementation of .gameherChallenge__trigger.

The use of flexbox ensures proper alignment and centering, consistent with existing patterns.

---

68-74: Consistent styling for .gameherChallenge__kpi.

The styling mirrors .col.gameherLeague__kpi, maintaining a consistent design approach.

---

93-94: Correct implementation of .gameherChallenge__button.

The toggle functionality is consistent with .gameherLeague__button, ensuring uniform behavior.

templates/views/tournaments.html.twig (1)

56-96: Well-structured "Game'Her Challenge" section.

The section is consistent with existing patterns and enhances user engagement with translatable elements and responsive design.