Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feat:Footer required in About us page #1160

Open
3 tasks done
likitha-kapu opened this issue Nov 2, 2024 · 4 comments · May be fixed by #1175
Open
3 tasks done

Feat:Footer required in About us page #1160

likitha-kapu opened this issue Nov 2, 2024 · 4 comments · May be fixed by #1175

Comments

@likitha-kapu
Copy link

Is there an existing issue raised for this?

  • I have searched the existing issues

Describe the feature

To create a footer for the "About Us" page that enhances navigation and provides essential information about the website, improving user experience and accessibility.The footer will serve multiple purposes: it will provide quick links to important sections of the website, display contact information, and present social media links for user engagement. The footer should be visually appealing and consistent with the overall design of the site, ensuring it fits seamlessly into the existing layout.
I want to make a footer similer to the one in your review page which looks like this
image

Add ScreenShots

At present there is no footer to about us page.It is looking this way:
image

Component

I want to add /footer component in the about us page

It should be implemented because

Objective:
The primary goal of adding a footer to the "About Us" page is to enhance user navigation, accessibility, and engagement. The footer will serve as a consolidated space for important links, contact information, and social media engagement, contributing to a more cohesive user experience across the website.

Components of the Footer
Quick Links:
Purpose: Provide easy access to other key pages, facilitating smoother navigation for users.
Use-Case: A visitor on the "About Us" page may want to quickly access the "Services" or "Contact Us" page without needing to return to the homepage. This is particularly useful for users who are interested in learning more about the organization or reaching out for inquiries.

Contact Information:
Purpose: Display essential contact details that users can easily reference.
Use-Case: Users who wish to inquire about services or have specific questions can find the phone number and email address readily available in the footer, encouraging them to reach out without searching through multiple pages.

Social Media Links:
Purpose: Provide links to the organization’s social media profiles, enhancing engagement and community building.
Use-Case: Users interested in following the organization on social media can find and access these links quickly. For example, if a user enjoys the content on the "About Us" page, they might want to connect further through Facebook or Instagram, fostering a deeper relationship with the brand.

Copyright Notice:
Purpose: Legally protect the content and acknowledge the ownership of the website.
Use-Case: Including a copyright statement reinforces the professionalism and legitimacy of the organization. It reassures users that they are interacting with a credible entity.

Would you like to work on this issue?

Yes

Terms & Conditions

  • I agree to follow the Code of Conduct
  • I'm a GSSOC'24 Ext contributor
Copy link
Contributor

github-actions bot commented Nov 2, 2024

👋 Thank you @likitha-kapu for raising an issue! We appreciate your effort in helping us improve. Our team will review it shortly. Stay tuned!

@likitha-kapu
Copy link
Author

@vishanurag please assign me this task under gssoc 24 and with hacktoberfest label

@likitha-kapu
Copy link
Author

@vishanurag is this okay
image

@likitha-kapu likitha-kapu linked a pull request Nov 3, 2024 that will close this issue
5 tasks
@likitha-kapu
Copy link
Author

@vishanurag please checkout my pull request

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants