T2834 Improve choose for me new sponsorship workflow

[Shayan105]

Summary

This PR introduces a new workflow to the sponsor when trying to sponsor a new child.

User story

As a user, I want to see profile card of the randomly sampled child before checking out.

New design descirption:

The "Choose for me button" does no longer redirect to the checkout. It shows the card of the randomly sampled child and allow the user to either randomly draw a new one or to see all possible child.

Video record of the new design :

Screencast.from.16.12.2025.13.17.05.webm

[gemini-code-assist]

Summary of Changes

Hello @Shayan105, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request significantly improves the user experience for the 'choose for me' sponsorship workflow. Instead of navigating to a new page, users will now see a randomly selected child's profile appear instantly on the current page. This change introduces new interactive elements, allowing users to easily choose another child or view all available children, making the process more fluid and engaging.

Highlights

• Dynamic 'Choose for Me' Workflow: The 'Choose for Me' functionality has been updated to dynamically display a randomly selected child on the same page, eliminating the need for a page redirect and providing a smoother user experience.
• Backend HTML Rendering: The backend now directly renders the HTML content for the randomly chosen child and returns it to the frontend, simplifying client-side rendering logic for this specific feature.
• Enhanced User Interface: New UI elements, including 'Choose another child' and 'See all children' buttons, have been introduced. The display messages and button visibility now adapt dynamically based on whether a child has been randomly selected.
• Code Refactoring: The animation logic for appending new results has been refactored into a dedicated _appendAndAnimate method in the JavaScript, improving code organization and reusability.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request refactors the 'Choose for me' sponsorship workflow to display the randomly selected child on the same page instead of redirecting. The changes are generally good, introducing a helper function for animations and updating the UI state accordingly. However, I've found a critical issue in the Python backend that could cause server errors, as well as a logic flaw in the JavaScript frontend that could lead to an inconsistent UI. I've also included some suggestions for minor cleanups and best practices in the JavaScript and XML template files. Addressing these points will improve the robustness and maintainability of the new workflow.