Welcome to the first lesson of our course on developing a personal tutor web application with FastAPI and DeepSeek! In this lesson, we will focus on setting up a basic tutor interface using FastAPI and HTML. This is an essential step in creating a user-friendly web application that enhances the learning experience. A well-designed interface is crucial for engaging students and ensuring they can interact with the tutor seamlessly.
To help you better visualize the interface we're building, here's a simple mockup of how the tutor web page will look after following the steps in this lesson:
- The header is at the top, welcoming the user.
- The messages area is in the center, where the conversation between the student and tutor appears.
- At the bottom, there is an input field for typing questions, a Send button, and a New Session button.
FastAPI is primarily designed as an API framework, but it also provides excellent support for serving HTML content through template engines. Unlike traditional web frameworks that focus heavily on server-side rendering, FastAPI gives you the flexibility to choose how to handle HTML content.
Jinja2 is a modern and designer-friendly templating language for Python, inspired by Django's template system. It's fast, widely used, and features a sandboxed execution environment, making it secure for rendering user-provided templates. Jinja2 allows you to:
- Insert dynamic Python variables into HTML
- Use control structures like loops and conditionals
- Extend and include templates for reusable components
- Apply filters to modify variables during rendering
By combining FastAPI with Jinja2, we get the best of both worlds: FastAPI's performance and modern API capabilities alongside Jinja2's powerful templating system for HTML generation.
To serve HTML templates with FastAPI, we first need to create a dedicated templates directory in our project. This directory will store all our HTML template files that will be rendered by the application.
The templates directory is placed at the root level of our project, making it easily accessible from our main application file. This organization follows the conventional structure for web applications and keeps our template files separate from the application logic.
Once we have our directory structure in place, we need to configure FastAPI to use Jinja2 for template rendering. This is done by importing and initializing the Jinja2Templates class in our main application file.
The Jinja2Templates class is initialized with the path to our templates directory. This creates a template engine that FastAPI will use to render HTML files. The directory="templates" parameter tells the engine where to look for template files.
With our templates directory and Jinja2 setup complete, we can now render HTML templates in our route handlers. This is done using the TemplateResponse class, which combines a template with context data to produce an HTML response.
In this route handler, we:
- Specify that the response should be HTML using
response_class=HTMLResponse - Use dependency injection to get or create a student ID
- Call
templates.TemplateResponseto render our template - Pass the template name (
"tutor.html") as the first argument - Provide a context dictionary as the second argument, which must include the
requestobject
The TemplateResponse will look for tutor.html in our templates directory, render it with the provided context, and return the resulting HTML to the client. This approach allows us to serve dynamic content while maintaining a clean separation between our application logic and presentation layer.
The HTML template for the tutor interface begins with the basic structure of an HTML document. This includes the <!DOCTYPE html> declaration, which defines the document type and version of HTML being used. The <html> tag wraps the entire content of the page, and within it, the <head> section is defined.
In the <head> section, we set the title of the page to "Your Personal Tutor", establishing the foundation for the tutor interface.
Moving into the <body> of the document, we start with a header section that sets the tone for the tutor interface. This section is designed to welcome students and encourage them to engage with the personal tutor.
The header includes a main heading (<h1>) and a paragraph (<p>), providing a friendly introduction to the tutoring service. This sets the stage for the interactive elements that follow.
Following the header, we define the tutor container, which is the core of the user interface. This section is responsible for displaying the conversation and providing input elements for student interaction.
The #messages div is where the conversation between the student and tutor will appear, while the input field and buttons allow students to type and send questions. The "Send" button triggers the sendQuery function, and the "New Session" button clears the conversation history, preparing the interface for a new tutoring session.
After setting up the HTML structure, we move on to adding interactivity to our tutor interface using JavaScript. This is done by placing a script section at the bottom of the HTML document, where we'll define the necessary JavaScript functions.
In this section, we create a script block within our HTML code to define JavaScript functions that enable interactivity in the tutor interface. By using plain JavaScript, we can directly manipulate HTML elements and handle user events. Placing the script at the end of the document ensures that all HTML elements are fully loaded before the script runs, preventing errors that might occur if the script tries to access elements that haven't been rendered yet. This approach allows us to seamlessly integrate JavaScript into our HTML, enhancing the functionality of our web application.
Before implementing the functions that handle tutor interactions, it's important to obtain references to the necessary DOM elements. This allows us to manipulate these elements directly within our JavaScript code.
By retrieving references to the messagesContainer and messageInput elements, we can easily update the tutor interface and handle student input. The messagesContainer is where the conversation will be displayed, and the messageInput is the field where students type their questions. These references are crucial for implementing the interactive functions that follow.
With the necessary DOM elements initialized, we can proceed to create functions that enhance the interactivity of our tutor interface. The startNewSession function is designed to clear the conversation history, allowing students to begin a fresh tutoring session. This function is triggered when the "New Session" button is clicked.
The startNewSession function clears all messages from the tutor interface, providing a clean slate for students to start a new learning session. This functionality is essential for resetting the conversation and enhancing the user experience by allowing multiple interactions without refreshing the page.
Additionally, by adding an event listener for the DOMContentLoaded event, we ensure that the startNewSession function is automatically called when the page finishes loading. This means the tutor interface is always initialized with a clean state, ready for student interaction as soon as the page is accessed. This approach enhances the learning experience by ensuring the tutor is ready to use immediately upon loading.
To effectively display the conversation in our tutor interface, we use the appendMessage function. This function creates a new message element, assigns it a CSS class based on the message's origin (user or assistant), appends it to the conversation container, and ensures the view scrolls to the latest message.
The appendMessage function is crucial for dynamically adding messages to the tutor interface. It creates a new <div> element for each message, assigns a class to differentiate between student and tutor messages, and appends it to the messagesContainer. This function also ensures that the conversation view automatically scrolls to the bottom, keeping the latest messages in view.
Building on the appendMessage function, the sendQuery function handles student input and updates the tutor interface. It processes the student's question, displays it, and simulates a response from the tutor. This function is triggered when the "Send" button is clicked or when the student presses Enter without holding Shift.
The sendQuery function is responsible for capturing the student's input, ensuring it's not empty, and then displaying it in the tutor interface using the appendMessage function. After sending the question, it clears the input field to prepare for the next question. It also simulates a response from the tutor by echoing the student's question back after a short delay, demonstrating basic interactivity in the tutoring application.
To enhance user experience, we can allow students to send questions by pressing the Enter key. This functionality is implemented by listening for the Enter key press event on the input field.
This code snippet listens for the keypress event on the messageInput field. When the Enter key is pressed without the Shift key, it prevents the default behavior (which would be to insert a newline) and calls the sendQuery function. This allows students to quickly send questions using the keyboard, improving the tutor interface's usability.
In this lesson, we covered the essential steps for setting up a basic tutor interface using FastAPI and HTML. We explored how FastAPI serves HTML templates using Jinja2 and how JavaScript is used to handle student interactions. By understanding the integration between FastAPI, HTML, and JavaScript, you have laid the groundwork for building a dynamic web application for personalized tutoring. As you move on to the practice exercises, focus on reinforcing these concepts and experimenting with the code to deepen your understanding. This foundational knowledge will be crucial as we continue to enhance the personal tutor's capabilities in future lessons.
