[RTY-260045]: Fix UI responsiveness, spacing issues, and sticky foote…

[Ravindrayadav04]

…r layout

Pull Request Template

Description

This PR improves overall UI/UX by fixing layout issues, ensuring responsive design, and implementing a sticky footer.

Fixes Implemented

1. Implemented proper sticky footer using flexbox layout:

   • Added .container wrapper with min-height: 100vh
   • Applied flex: 1 to main content
   • Used margin-top: auto for footer

2. Reduced unnecessary top spacing:

   • Adjusted margins and padding in .main-layout and .hero

3. Improved mobile responsiveness:

   • Standardized breakpoint to 700px
   • Reduced font sizes for headings, inputs, and buttons
   • Converted input layout to column for smaller screens

4. Fixed spacing issues in Recent section:

   • Reduced gap between .recent-header and .scroll-container

5. Improved UI alignment:

   • Adjusted button sizes and layout for better mobile visibility

Type of change

• Sticky footer implemented using flexbox
• Reduced excessive white space
• Improved mobile layout (font sizes, input width, buttons)
• Fixed spacing in "Recently Shortened" section
• Standardized responsive breakpoints

##screenshots

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

• Test A
• Test B

Test Configuration:

• Browser:
• Device:
• Toolchain:

Checklist

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• Any dependent changes have been merged and published in downstream modules
• I have checked my code and corrected any misspellings