-
-
Notifications
You must be signed in to change notification settings - Fork 751
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
[BUG] Dynamic Grid Layout for Case Studies Page Based on Number of Items #3566
Comments
Welcome to AsyncAPI. Thanks a lot for reporting your first issue. Please check out our contributors guide and the instructions about a basic recommended setup useful for opening a pull request. |
Please assign me the issue I would like to contribute. |
I would like to start with this issue if no one is working on this, please assign me with the issue. |
It's awaiting triage and is already being worked on. You can check other issues in the meantime. Ideally, the PR created after the issue is validated by a triager/maintainer should be considered with the priority given to PR opened by the issue author. |
/assign |
@Aditya-Prakash14 please read contributing guidelines. We need to wait for triage from one of the maintainer. |
Describe the bug.
The current implementation of the Case Studies page uses a hardcoded grid-cols-3 class for the grid layout. This causes an issue when there are fewer than 3 items (e.g., only 2 case studies), resulting in uneven spacing and a less aesthetically pleasing layout.
Expected behavior
The grid should adjust based on the number of case studies available. If there are fewer than 3 items (e.g., 2 or 1), the grid should dynamically adjust to display them in a more appropriate layout (e.g., grid-cols-2 for 2 items, grid-cols-1 for 1 item).
Screenshots
How to Reproduce
Steps to Reproduce:
🥦 Browser
Google Chrome
👀 Have you checked for similar open issues?
🏢 Have you read the Contributing Guidelines?
Are you willing to work on this issue ?
Yes I am willing to submit a PR!
The text was updated successfully, but these errors were encountered: