Change wording from New content to Recent features on version home pages; update links

[josh-wong]

Description

This PR updates the "New content" section across multiple language and version-specific files to rename it to "Recent features" and improve its structure and clarity. The changes include renaming variables, updating comments, modifying CSS class names, and adjusting content to reflect recent features introduced in the documentation.

Related issues and/or PRs

• Home page redesign originally implemented in Redesign version home pages #1346.

Changes made

• Renamed new_content to recentFeatures and updated the section title from "New content" to "Recent features" in files for versions 3.13, 3.14, 3.15, and 3.16, as well as their Japanese counterparts. Updated comments to clarify the purpose of links and labels. (src/components/Cards/3.13.tsx, src/components/Cards/3.14.tsx, src/components/Cards/3.15.tsx, src/components/Cards/3.16.tsx, src/components/Cards/ja-jp/3.13.tsx, src/components/Cards/ja-jp/3.14.tsx, src/components/Cards/ja-jp/3.15.tsx, src/components/Cards/ja-jp/3.16.tsx) [1] [2] [3] [4] [5] [6]
• Updated CSS class names from new-content-* to recent-features-* to align with the renaming of the section. (src/components/Cards/3.13.tsx, src/components/Cards/3.14.tsx, src/components/Cards/3.15.tsx, src/components/Cards/3.16.tsx, src/components/Cards/ja-jp/3.13.tsx, src/components/Cards/ja-jp/3.14.tsx, src/components/Cards/ja-jp/3.15.tsx, src/components/Cards/ja-jp/3.16.tsx) [1] [2] [3] [4] [5] [6]
• Adjusted the content of the "Recent features" section to include updated links and labels for newly introduced features, ensuring alignment with the documentation for each version and language. (src/components/Cards/3.13.tsx, src/components/Cards/3.14.tsx, src/components/Cards/3.15.tsx, src/components/Cards/3.16.tsx, src/components/Cards/ja-jp/3.13.tsx, src/components/Cards/ja-jp/3.14.tsx, src/components/Cards/ja-jp/3.15.tsx, src/components/Cards/ja-jp/3.16.tsx) [1] [2] [3] [4] [5] [6]

Checklist

The following is a best-effort checklist. If any items in this checklist are not applicable to this PR or are dependent on other, unmerged PRs, please still mark the checkboxes after you have read and understood each item.

• I have updated the side navigation as necessary.
• I have commented my code, particularly in hard-to-understand areas.
• I have updated the documentation to reflect the changes.
• Any remaining open issues linked to this PR are documented and up-to-date (Jira, GitHub, etc.).
• My changes generate no new warnings.
• Any dependent changes in other PRs have been merged and published.

Additional notes (optional)

N/A

[gemini-code-assist]

Summary of Changes

Hello @josh-wong, 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 focuses on enhancing the clarity and accuracy of the documentation home pages by renaming the 'New content' section to 'Recent features'. This change involves a comprehensive update of variable names, CSS classes, and the actual content links to better reflect the purpose of the section and showcase recent product developments.

Highlights

• Wording Change: The section title 'New content' has been globally updated to 'Recent features' across all relevant version-specific and language-specific home pages (3.13, 3.14, 3.15, 3.16, and their Japanese counterparts).
• Code Refactoring: The variable new_content has been renamed to recentFeatures in the affected React components, improving code readability and consistency with the new section title.
• CSS Updates: Corresponding CSS class names (e.g., new-content-icon, new-content-cell) have been updated to recent-features-icon and recent-features-cell to align with the new terminology.
• Content Refresh: The links and labels within the 'Recent features' section have been adjusted to highlight newly introduced features and ensure the documentation is up-to-date for each version.

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 in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.

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 issue 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 is currently in preview and 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 to provide feedback.

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 renames the 'New content' section to 'Recent features' across multiple files, improving clarity and consistency. The changes include updating variable names, modifying CSS classes, and refreshing the content links. There are a few instances where the new guideline about avoiding anchor links is not followed, which I've pointed out in the comments.