-
-
Notifications
You must be signed in to change notification settings - Fork 697
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] Testimonials on the "What the experts are saying" section of the webpage are not aligned consistently. #3487
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. |
Hey, this is Balraj, A positive response expected. 😄 |
Hi @BalrajDhakad @subrajeet-maharana, this issue is created by me(not a maintainer) and i will be working on it, please feel free to create your own unique issue to raise a PR. |
Okay, |
Hi, that is not a fix it is altering the text. You cant change or alter the
original document.
…On Fri, 20 Dec 2024 at 8:15 AM, Balraj Dhakad ***@***.***> wrote:
Okay,
It is an easy fix, you can simply increase the length of the paragraph and
it will take that blank space.
Because changing the CSS will not work there.
—
Reply to this email directly, view it on GitHub
<#3487 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AR4CQ4ASFO6PJKWQMUVI3ML2GOAFRAVCNFSM6AAAAABT4VKYE6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNJWGE2TKMRXGY>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
That doesn't look like an actual improvement that we require at the moment |
Describe the bug.
Expected behavior
All testimonials should take up equal space, maintaining consistent vertical alignment across rows for a balanced layout.
Screenshots
How 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: