-
Notifications
You must be signed in to change notification settings - Fork 420
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 CHANGE] : UI Changes in Iskcon Events Page #1782
Comments
Congratulations, @aarushi-taori! 🎉 Thank you for creating your issue for Moksh. Your contribution is greatly appreciated and we look forward to working with you to resolve the issue. Keep up the great work! Should you have any queries or require guidance, do not hesitate to ask. |
@swapnilgarg7 @rohansx @visparmar @ankitjt Please assign me this issue |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description:
Make the Structure and UI of the Iskcon Events Page more uniform and attractive.
[Provide a clear and concise description of the style change you are requesting.]
Reason for Change:
[Explain the reasons behind the requested style change, such as usability, branding, or user experience.]
Current Styling:
[Describe the current styling that needs to be changed.]
Proposed Styling:
[Describe the desired styling or changes you would like to see.]
Screenshots or Design Mockups (optional):
[If available, include relevant screenshots or design mockups illustrating the requested style changes.]
Additional Information (optional):
[Provide any additional information that may help in understanding or implementing the style change. This can include any specific requirements or constraints.]
Priority Level (optional):
Timeline (optional):
[Specify any preferred or required timeline for implementing the style change.]
Possible Implementation Approach (optional):
[If you have any suggestions or ideas on how the style change could be implemented, feel free to provide them here.]
The text was updated successfully, but these errors were encountered: