Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Footer displays on the right side of the page instead of at the bottom

Open Beginner friendly
#452 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
84/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
css, html, javascript
Domain
frontend

Research direction

Start by comparing the footer and .footer rules in app/static/css/custom.css with the footer wrapper in app/templates/base.html, especially in light of commit 4d91ebda. Reproduce the layout on the Home page with the “Create a Deadline” form, then adjust the relevant layout so the footer spans below the content. Done means it appears at the bottom rather than as a right-side panel.

Written by the indexing model from the issue text.

Description

Description

The footer ("Created & Designed by the Student Software Developers Group. Comments? Questions? Concerns? Email Us") renders as a vertical dark panel on the right side of the page instead of spanning the bottom.

Image

Steps to reproduce

  1. Log in and open the page with the "Create a Deadline" form (Home).
  2. Observe the footer placement.

Expected behavior

The footer appears at the bottom of the page, below the main content.

Image

Actual behavior

The footer is displayed beside the content, as a dark column on the right edge running the full page height.

Notes

  • Likely related to the recent "Remove fixed footer" change (4d91ebda). Check the footer / .footer rules in app/static/css/custom.css and the <footer> wrapper in app/templates/base.html.
Dominant language
JavaScript
Stars
0
Forks
2
Avg merge
6d 21h
Merged PRs (30d)
1

Getting set up

Open in Codespaces

Starts the project's dev container in your browser, under your own GitHub account.

  • No Dockerfile or Docker Compose file
  • No pull request template
  • No contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from BCStudentSoftwareDevTeam/cas

All issues in BCStudentSoftwareDevTeam/cas

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.