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

[style]: Improve Color Scheme for Subscribe Section #3296

Open
4 of 5 tasks
akshay0611 opened this issue Nov 17, 2024 · 1 comment · May be fixed by #3297
Open
4 of 5 tasks

[style]: Improve Color Scheme for Subscribe Section #3296

akshay0611 opened this issue Nov 17, 2024 · 1 comment · May be fixed by #3297
Labels
enhancement New feature or request

Comments

@akshay0611
Copy link
Contributor

What's the style idea?

Description of Style Idea:

We need to address the inconsistent text colors in the Subscribe Section across different pages. The current design has the following issue:

  • Inconsistent text colors between different pages (e.g., finance.html and contact.html).

Suggestions for Improvement:

  • Add a consistent color scheme (e.g., #2e2e2e for headings, aligned with the overall theme).

Add screenshots

Current Design (finance.html):

Screenshot 2024-11-17 at 8 01 19 PM

Current Design (contact.html):

Screenshot 2024-11-17 at 8 00 55 PM

Code of Conduct

  • I agree to follow this project's Code of Conduct
  • I have read the Contributing Guidelines
  • I agree to follow this project's Code of Conduct
  • I'm a GSSoC'24 contributor
  • I want to work on this issue
@akshay0611 akshay0611 added the enhancement New feature or request label Nov 17, 2024
Copy link

👋 Thanks for opening this issue! We appreciate your contribution. Please make sure you’ve provided all the necessary details and screenshots, and don't forget to follow our Guidelines and Code of Conduct. Happy coding! 🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant