UI/new Login register page updated (SWOC'26)

[U-jjwal]

Description

This PR improves the UI/UX of the platform by making the interface cleaner, more modern, and more user-friendly. The main changes include:

• Updated styling and layout of the Login page
• Updated styling and layout of the Register page
• Improved the Hero section with better spacing, readability, and visual hierarchy
• Added smooth scrolling for a more polished browsing experience

All existing functionality remains unchanged — this update focuses only on UI/UX enhancement.

---

Related Issue

Fixes #30

---

Type of Change

• Bug Fix
• UI/UX Improvement
• New Feature
• Documentation Update
• Other (please describe):

---

Screenshots (Before / After)

(Attach your screenshots here — Login, Register, Hero)

---

How Has This Been Tested?

• Manually tested UI in browser
• Tested responsiveness
• Confirmed no auth or routing logic was affected

---

Checklist

• My code follows the project coding guidelines
• I have linked the issue number correctly
• I have added screenshots where applicable
• I am contributing under SWOC’26
• I have tested my changes locally

---

Program

Contribution under SWOC’26.

[netlify]

✅ Deploy Preview for smartrentsystem ready!

Built without sensitive environment variables

Name	Link
🔨 Latest commit	84eae4b
🔍 Latest deploy log	https://app.netlify.com/projects/smartrentsystem/deploys/69582688dc2d3a0009f9fcc6
😎 Deploy Preview	https://deploy-preview-50--smartrentsystem.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

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

[hitesh-kumar123]

add issue number

[U-jjwal]

issue #30

[hitesh-kumar123]

follow pr templates without pr templates not approve your pr

[U-jjwal]

ok

[U-jjwal]

i have fixed the pr template issue

[hitesh-kumar123]

Please understand that this is not a joke.

You have not added before/after screenshots, and you also did not clearly explain what changes you made in this pull request. As a project admin, it becomes very difficult for me to understand what exactly was changed and why.

When I open the preview, I can see that many frontend parts of the website have been modified, but there is no proper explanation, no testing details, and no confirmation that everything was checked before creating the PR. It feels like the PR was created directly without fully verifying the changes.

Please carefully review your changes, test the website properly, and fix any issues before requesting a merge. After merging, it becomes harder to track and fix problems.

If the PR includes UI changes, you must add before/after screenshots and clearly describe:

What was changed

Why it was changed

What you tested

Once the PR follows the template properly and all changes are verified, I will be able to review and merge it.