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: Convert Classnames on All Pages to follow BEM naming Convention #604

Closed
4 tasks done
shreyash3087 opened this issue Jun 23, 2024 · 3 comments
Closed
4 tasks done
Assignees
Labels
assigned u r assigned to the issue enhancement New feature or request good issue Good for newcomers gssoc'24 level3

Comments

@shreyash3087
Copy link
Contributor

Describe the feature

To improve the maintainability, scalability, and readability of our CSS, we need to refactor the class names across all pages of the website to follow the BEM (Block, Element, Modifier) naming convention. The BEM methodology helps create reusable and modular code, making it easier to manage and less prone to conflicts.

Tasks:

  • Review Current Class Names
  • Refactor Class Names
  • Update Stylesheets
  • Update JavaScript

Add ScreenShots

N/A

Record

  • I agree to follow this project's Code of Conduct
  • I'm a GSSOC'24 contributor
  • I'm a VSoC'24 contributor
  • I want to work on this issue
@shreyash3087 shreyash3087 added the enhancement New feature or request label Jun 23, 2024
Copy link

Thank you for creating this issue! 🎉 We'll look into it as soon as possible. In the meantime, please make sure to provide all the necessary details and context. If you have any questions or additional information, feel free to add them here. Your contributions are highly appreciated! 😊

You can also check our CONTRIBUTING.md for guidelines on contributing to this project.

@mdazfar2 mdazfar2 added good issue Good for newcomers gssoc'24 level3 assigned u r assigned to the issue VSoC'24 labels Jun 23, 2024
@mdazfar2
Copy link
Owner

@shreyash3087 Issue acknowledged. Task assigned to you.

@shreyash3087 shreyash3087 closed this as not planned Won't fix, can't repro, duplicate, stale Jun 25, 2024
Copy link

Hello @shreyash3087! Your issue #604 has been closed. Thank you for your contribution!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
assigned u r assigned to the issue enhancement New feature or request good issue Good for newcomers gssoc'24 level3
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants