Add prerequisites section to image classification from scratch example

[Parshv-sudo]

Summary
Adds a short “Prerequisites” section to the Image classification from scratch example,
outlining the expected background knowledge and linking to relevant Keras guides and recipes.

Motivation
Improves onboarding by helping readers assess readiness before diving into the example,
as discussed in #2151.

Scope
Documentation-only change; no code behavior is modified.

[google-cla]

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

[gemini-code-assist]

Summary of Changes

Hello @Parshv-sudo, 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 improves the onboarding experience for the 'Image classification from scratch' example by introducing a clear 'Prerequisites' section. This addition helps users quickly assess their readiness by detailing the necessary foundational knowledge and providing links to relevant Keras documentation. The changes are purely documentation-focused and do not alter any existing code functionality.

Highlights

• New Prerequisites Section: A new 'Prerequisites' section has been added to the 'Image classification from scratch' example, both in its Jupyter Notebook and Markdown versions.
• Educational Content: This section outlines essential background knowledge required for the example, covering basic Python/NumPy, the Keras Functional API, Keras built-in training methods, and fundamental CNN concepts.
• Resource Links: Relevant links to Keras guides and recipes are included within the prerequisites to help readers deepen their understanding.
• Minor Formatting and Metadata Updates: Minor formatting adjustments were made by removing trailing empty lines in some code cells, and the Python version metadata in the Jupyter Notebook was updated from 3.7.0 to 3.10.11.

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 adds a helpful "Prerequisites" section to the "Image classification from scratch" example, which is a great improvement for user onboarding. However, there are a couple of issues in the implementation. In the Jupyter notebook, the new section is incorrectly added as a code cell, leading to a SyntaxError. It should be a markdown cell. In the corresponding Markdown file, the new section is wrapped in """, which is not standard Markdown and will likely render incorrectly. I've provided suggestions to correct these issues and also to improve the formatting of URLs to be consistent with the rest of the documentation.

[Parshv-sudo]

Hi @sachinprasadhs,
I’m following up on this PR.
I’ve addressed the review feedback by changing the notebook cell to Markdown and correcting the Markdown syntax and links in the .md file. Whenever you have a moment, I’d appreciate a quick look.
Thanks!