Update index.html for updated banner - post website switchover

[juliebates]

change banner message to point to new site location, note that legacy content here will remain available.

[gemini-code-assist]

Summary of Changes

Hello @juliebates, 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 updates the index.html file to reflect a recent website switchover for ReproNim. It changes the prominent banner message to direct users to the new repronim.org site and clarifies that the current site now serves as a legacy archive, retaining all its previous content. This ensures users are correctly informed about the new primary website while still having access to historical information.

Highlights

• Website Banner Update: The main banner message on index.html has been updated to inform users that ReproNim's new website is now live at repronim.org.
• Legacy Site Clarification: The updated banner explicitly states that the current site is now ReproNim's legacy site and that all previously available content remains accessible here.

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 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 updates the banner on the main page to reflect the website switchover. The new text correctly informs users about the new site and the status of the current one as a legacy site. I've added a couple of suggestions to improve user experience by making the new site URL a clickable link, and to improve code maintainability by moving inline styles to a separate CSS file.

[gemini-code-assist]

For better user experience, it's recommended to make 'repronim.org' a clickable link. This allows users to easily navigate to the new website. The suggested change also combines the text onto a single line for better code readability.

                    <h2 class="section-heading text-center" style="background-color: #fafc92; padding: 0.5em;">See ReproNim’s new website at <a href="https://www.repronim.org">repronim.org</a>. This is now ReproNim’s legacy site. All the content previously available on our old site continues to be available here.</h2>

[gemini-code-assist]

For better maintainability and separation of concerns, it's good practice to avoid inline styles. Consider moving the style attribute content to a dedicated CSS class in an external stylesheet, like css/style.css which is already being used. For example, you could create a .promo-banner class and add the styling there.