Content/2026 02 23

[chrismclarke]

What does this PR do?

• Please include a summary of the change(s) and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change.

How should this be manually tested?

• Please include the steps to be done inorder to setup and test this PR.
• Ensure any data required has been exported via yarn scripts strapi export

What are the relevant github issues?

Screenshots

[gemini-code-assist]

Summary of Changes

Hello @chrismclarke, 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 primarily focuses on updating and synchronizing content within the application's database. It introduces new annual report data, refreshes information related to summer camps, and adjusts various HTML and action button components. The changes also involve adding a new PDF document and ensuring that the database's internal sequence numbers are correctly updated to reflect these content modifications, maintaining data integrity and consistency across the platform.

Highlights

• Content Updates: Multiple content files have been updated, including annual reports, action buttons, and various HTML content blocks. This includes adding new annual report entries for 2025 and updating summer camp information to reflect 'Summer 2026 Update' with new details and an embedded Datawrapper chart.
• Database Synchronization: The database sequence numbers for several tables have been incremented to reflect the addition and modification of content entries. This ensures consistency across the content management system's data.
• File Management: A new PDF file for the 'Feb 2025 Annual report SAMI' has been added to the system, along with its corresponding links to folders and related annual report entities. Some old image and HTML content entries have been removed.
• Volunteer Content Structure: The structure and mapping of components for volunteer content have been revised, including updates to component IDs, entity IDs, and the reordering of associated FAQs.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Changelog

• config/development.env
  • Updated the RESEND_API_KEY with a placeholder value.
• data/db-json/annual_reports.json
  • Added two new annual report entries for the year 2025.
• data/db-json/components_common_action_buttons.json
  • Removed an 'Apply Now' action button with ID 8.
  • Added a new 'Apply Now' action button with ID 43.
• data/db-json/components_common_htmls.json
  • Removed several old HTML content blocks (IDs 1, 2, 3, 37).
  • Updated the 'Summer 2025 Update' HTML content (ID 93) to 'Summer 2026 Update' with revised camp details and a new list format.
  • Added new HTML content blocks, including an embedded Datawrapper iframe (IDs 419, 445, 446, 447, 448, 449).
• data/db-json/components_common_images.json
  • Removed two image entries with IDs 12 and 34.
• data/db-json/files.json
  • Updated the updated_at timestamp for an existing SVG file.
  • Added a new PDF file entry for 'Feb 2025 Annual report SAMI'.
• data/db-json/files_folder_lnk.json
  • Added a new link associating the new PDF file (ID 223) with folder ID 2.
• data/db-json/files_related_mph.json
  • Removed two file-related entries (IDs 395 and 505).
  • Added new file-related entries linking the new annual reports (IDs 28, 29) to the new PDF file (ID 223) and a cover image (ID 116).
• data/db-json/sqlite_sequence.json
  • Updated the sequence number for annual_reports to 29.
  • Updated the sequence number for components_common_action_buttons to 43.
  • Updated the sequence number for components_common_htmls to 449.
  • Updated the sequence number for components_common_images to 113.
  • Updated the sequence number for files to 223.
  • Updated the sequence number for files_folder_lnk to 151.
  • Updated the sequence number for files_related_mph to 725.
  • Updated the sequence number for volunteer_contents to 12.
  • Updated the sequence number for volunteer_contents_cmps to 238.
  • Updated the sequence number for volunteer_contents_faqs_lnk to 187.
• data/db-json/volunteer_contents.json
  • Updated the id, published_at, updated_at, and updated_by_id for existing volunteer content entries.
  • Modified the id of the first entry from 1 to 3.
  • Modified the id of the second entry from 3 to 12.
• data/db-json/volunteer_contents_cmps.json
  • Updated cmp_id, entity_id, and id values for multiple component mappings.
  • Changed component type for id: 229 from common.image to common.html.
• data/db-json/volunteer_contents_faqs_lnk.json
  • Removed a large block of FAQ links associated with volunteer_content_id: 1.
  • Added a new set of FAQ links associated with volunteer_content_id: 12.

Activity

• No specific activity (comments, reviews, progress) was provided in the pull request context.

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 primarily focuses on updating content data for the volunteer page and annual reports, along with a configuration change in the development environment. The changes include converting the SAMI map from an image to an embedded HTML iframe, updating the 'Summer Update' content to 2026, and adding the 2025 annual report. While the data updates are consistent with the intended content refresh, there are several instances of redundant component data and a security concern regarding a hardcoded API key in the configuration file.

[gemini-code-assist]

This entry (ID 446) is an exact duplicate of the entry with ID 93 (lines 342-345). Similarly, ID 447 (lines 935-937) is a duplicate of ID 419 (lines 923-925). This redundancy in the component tables leads to unnecessary data bloat. It is recommended to reuse existing component IDs across different versions (draft/published) of the content where possible, rather than creating identical new instances.

[gemini-code-assist]

This new action button entry (ID 43) is identical to the existing entry with ID 34 (lines 196-199). Re-creating identical components instead of referencing existing ones increases the maintenance burden and data size. Consider consolidating these entries to maintain a cleaner database state.