Skip to content

Conversation

@jagpreetrahi
Copy link

Description

This PR fixes #2427

Notes for Reviewers
This PR introduces the improvement of Getting Started section UI/UX for the mobile devices. It changes the styles related to the heading and paragraph tag.

Current Behavior
Screen Shot 2025-11-11 at 15 42 46

Expected Behavior
Screen Shot 2025-11-11 at 15 31 32

Signed commits

  • Yes, I signed my commits.

@welcome
Copy link

welcome bot commented Nov 11, 2025

Yay, your first pull request! 👍 A contributor will be by to give feedback soon. In the meantime, please review the Newcomers' Guide and sure to join the community Slack.
Be sure to double-check that you have signed your commits. Here are instructions for making signing an implicit activity while peforming a commit.

@gemini-code-assist
Copy link
Contributor

Summary of Changes

Hello @jagpreetrahi, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request focuses on improving the user interface and experience of the 'Getting Started' section, specifically targeting mobile device responsiveness. The changes involve subtle adjustments to spacing, text alignment, and font sizing to ensure a more polished and readable layout on smaller screens, addressing a reported UI/UX issue.

Highlights

  • Mobile UI/UX Improvements: Enhanced the visual presentation of the 'Getting Started' section on mobile devices by refining heading and paragraph styles for better readability and layout.
  • HTML Structure Adjustments: Modified _includes/getting-started.html to adjust spacing for step numbers, add a margin-top to paragraphs, and apply a new special-step class to a specific heading.
  • CSS Styling Refinements: Updated _sass/layout.scss to center and clamp the font size of the main 'Getting Started' heading, and introduced a white-space: nowrap property for the new special-step class to prevent text wrapping.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

@netlify
Copy link

netlify bot commented Nov 11, 2025

Deploy Preview for mesheryio-preview ready!

Name Link
🔨 Latest commit 87f4c98
🔍 Latest deploy log https://app.netlify.com/projects/mesheryio-preview/deploys/69130c7eb8ff720008bc90bc
😎 Deploy Preview https://deploy-preview-2431--mesheryio-preview.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request improves the UI/UX of the 'Getting Started' section for mobile devices by adjusting font sizes and layout. The SCSS changes are well-implemented, using modern features like clamp() for responsive typography. My main feedback concerns the use of inline styles in the HTML file, which can impact maintainability. I've provided specific suggestions to move these styles to the corresponding SCSS file. Overall, these changes are a good step towards a better mobile experience.

<div style="display: inline-flex; line-height: 60px;">
<h1 class="step-number" style="margin-right: 0.5rem">01</h1>
<h2 class="step-heading">Use Meshery Playground</h2>
<h1 class="step-number" style="margin-right: 0.3rem">01</h1>
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

To improve maintainability and adhere to best practices of separating structure (HTML) from presentation (CSS), please avoid using inline styles. The margin-right: 0.3rem should be moved to the .step-number class definition in your SCSS file. The same applies to line 22.

<h1 class="step-number">01</h1>

<h2 class="step-heading special-step">Use Meshery Playground</h2>
</div>
<p class="grey-bg-text" style="font-size: 1.15rem;">
<p class="grey-bg-text" style="font-size: 1.15rem; margin-top: 5px;">
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

Please move the inline style margin-top: 5px; to the .grey-bg-text class in your SCSS file. This helps in keeping the styling separate from the HTML structure, making the code cleaner and easier to maintain. The same applies to line 25.

<p class="grey-bg-text" style="font-size: 1.15rem;">

Copy link
Contributor

@Rajesh-Nagarajan-11 Rajesh-Nagarajan-11 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

image in 375px its overflow please fix that .

@jagpreetrahi
Copy link
Author

Alright, I do

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Improve the UI/UX of Getting Started section for the mobile device.

2 participants