Added allauth base template

[priyankaChauhan2804]

User description

closes #3415

Description: This update includes the base template for Django AllAuth under the template folder, ensuring a consistent layout for authentication-related pages. The base template provides a structured foundation for login, signup, and other authentication views.

---

PR Type

Enhancement, Bug fix

---

Description

• Introduced a new auth_base.html template for consistent authentication page layouts.

• Updated login.html, logout.html, and signup.html to extend auth_base.html.

• Added customizable blocks in auth_base.html for titles, descriptions, forms, and footers.

• Improved maintainability and consistency of authentication-related templates.

---

Changes walkthrough 📝

Relevant files

Enhancement

login.html Updated login page to use `auth_base.html`                              website/templates/account/login.html Changed base template from base.html to auth_base.html. Ensures consistent layout for the login page. +1/-1      logout.html Updated logout page to use `auth_base.html`                            website/templates/account/logout.html Changed base template from base.html to auth_base.html. Ensures consistent layout for the logout page. +1/-1      signup.html Updated signup page to use `auth_base.html`                            website/templates/account/signup.html Changed base template from base.html to auth_base.html. Ensures consistent layout for the signup page. +1/-1      auth_base.html Added new `auth_base.html` template                                            website/templates/auth_base.html Added a new base template for authentication pages. Includes customizable blocks for titles, descriptions, forms, and footers. Provides a consistent structure for authentication-related templates. +30/-0

---

Need help?

Type /help how to ... in the comments thread for any questions about PR-Agent usage.

Check out the documentation for more information.

Summary by CodeRabbit

• New Features
  • Introduced a dedicated authentication layout that enhances the overall design and responsiveness of login, logout, and signup pages.
  • Added a new base template specifically for authentication-related content.
• Refactor
  • Updated authentication-related pages to adopt the new layout, ensuring a more consistent and modern user experience across the site.

[github-actions[bot]]

PR Reviewer Guide 🔍

Here are some key observations to aid the review process:

🎫 Ticket compliance analysis 🔶 3415 - Partially compliant Compliant requirements: Add a base template for Django AllAuth pages to ensure consistent layout across authentication-related pages. Ensure the base template is used by all relevant AllAuth templates, such as login, logout, and signup. Provide customizable blocks for titles, descriptions, forms, and footers in the base template. Non-compliant requirements: [] Requires further human verification: []

⏱️ Estimated effort to review: 2 🔵🔵⚪⚪⚪

🧪 No relevant tests

🔒 No security concerns identified

⚡ Recommended focus areas for review Styling Placeholder The CSS styles in the auth_base.html template are currently placeholders (/* Your styles here */). Ensure that this is intentional and that the final styles will be added or handled elsewhere. <style> .auth-container { /* Your styles here */

[github-actions[bot]]

PR Code Suggestions ✨

[coderabbitai[bot]]

Walkthrough

This pull request updates the template inheritance for account pages by switching from the standard base template to a new authentication-specific base template. The login, logout, and signup pages now extend auth_base.html instead of base.html. Additionally, a new template file, auth_base.html, has been added. This template extends base.html and defines authentication-specific blocks (title, description, form, and footer) to standardize the layout for authentication-related views.

Changes

File(s)	Change Summary
website/templates/account/{login,logout,signup}.html	Updated template inheritance: {% extends "base.html" %} → {% extends "auth_base.html" %}.
website/templates/.../auth_base.html	Added new authentication base template extending base.html with blocks for title, description, form, and footer.

Assessment against linked issues

Objective	Addressed	Explanation
Fix all the allauth pages (#3415)	✅

Possibly related PRs

• OWASP-BLT/BLT#3970: The changes in the main PR focus on updating the template inheritance in the login.html, logout.html, and signup.html files, while the retrieved PR modifies the action attributes in the same files to include a redirect parameter; thus, they are related through their modifications to the same templates.

[!TIP]

⚡🧪 Multi-step agentic review comment chat (experimental)

• We're introducing multi-step agentic chat in review comments. This experimental feature enhances review discussions with the CodeRabbit agentic chat by enabling advanced interactions, including the ability to create pull requests directly from comments. - To enable this feature, set early_access to true under in the settings.

---

📜 Recent review details

Configuration used: CodeRabbit UI Review profile: CHILL Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 995c5aa6000f58dcdecd6b558960c1180551a5ce and d1b989db9fdf48a938af08060aea83adeb5b552c.

📒 Files selected for processing (3)

• website/templates/account/login.html (1 hunks)
• website/templates/account/logout.html (1 hunks)
• website/templates/account/signup.html (1 hunks)

🚧 Files skipped from review as they are similar to previous changes (3)

• website/templates/account/signup.html
• website/templates/account/logout.html
• website/templates/account/login.html

⏰ Context from checks skipped due to timeout of 90000ms (4)

• GitHub Check: Run Tests
• GitHub Check: docker-test
• GitHub Check: Analyze (python)
• GitHub Check: Analyze (javascript-typescript)

---

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[priyankaChauhan2804]

Please remove and style tags and use tailwind. Would you also show a screenshot of the forgot password page?

sir by any chance, is this the page you want?

[DonnieBLT]

@priyankaChauhan2804 please see the @coderabbitai suggestion, otherwise this looks good to merge once that is resolved. Thank you.

[coderabbitai[bot]]

[!TIP] For best results, initiate chat on the files or code changes.

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
# Check the content of auth_base.html to verify placeholder styles
cat website/templates/auth_base.html

Length of output: 951

---

@DonnieBLT I've examined the `auth_base.html` file and can confirm that it's already properly using Tailwind CSS classes (flex, min-h-screen, bg-white, shadow-lg, rounded-lg, etc.) and doesn't contain any placeholder styles that were mentioned in the CodeRabbit suggestion ("/* Your styles here */").

The template appears to be correctly implemented with Tailwind CSS classes for responsive design and styling. The CodeRabbit concern about placeholder styles seems to be inaccurate based on the current implementation. The PR should be good to merge as is.