You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The text / answer in under all the questions in the FAQs section is way to light for reading. This poses as setback and reduces the user friendly nature of the FAQ page. Please assign me this issue under the gssoc-ext and hacktober fest tag.
Expected behavior
I would like the change the style , more specifically the color scheme of the text in order to make it more readable for the users.
Add ScreenShots
See the text is barely visible.
On which device are you experiencing this bug?
Windows
Record
I have read the Contributing Guidelines
I'm a GSSOC'24 contributor
I have starred the repository
The text was updated successfully, but these errors were encountered:
Hi there! Thanks for opening this issue. We appreciate your contribution to this open-source project. We aim to respond or assign your issue as soon as possible.
The text / answer in under all the questions in the FAQs section is way to light for reading. This poses as setback and reduces the user friendly nature of the FAQ page. Please assign me this issue under the gssoc-ext and hacktober fest tag.
Expected behavior
I would like the change the style , more specifically the color scheme of the text in order to make it more readable for the users.
Is there an existing issue for this?
Describe the bug
The text / answer in under all the questions in the FAQs section is way to light for reading. This poses as setback and reduces the user friendly nature of the FAQ page. Please assign me this issue under the gssoc-ext and hacktober fest tag.
Expected behavior
I would like the change the style , more specifically the color scheme of the text in order to make it more readable for the users.
Add ScreenShots
See the text is barely visible.
On which device are you experiencing this bug?
Windows
Record
The text was updated successfully, but these errors were encountered: