changed index.css file added animations and structured the text and font size and added section.css file for better UI

[Komal-bendresh]

🔖 PR Title:

Enhanced UI Components with Modern Animations and Section Styling

---

📄 Description:

Added modern UI components, smooth animations, and standardized section styling to improve user experience and visual consistency across the platform.

• Enhancement 🔧
• Documentation 📝
• UI/UX Update 🎨

---

🧑‍💻 What changes were made?

• Added glass morphism effects and smooth animations to cards and sections
• Standardized styling for About, Who Are We, Our Commitment, and AKTU sections
• Enhanced text alignment and responsiveness
• Implemented smoother transitions using cubic-bezier
• Added floating animations for interactive elements
• Improved section headers with gradient effects

---

📚 Documentation Updated?

• Yes, I have updated the relevant section in README.md or related files.

---

🖼️ Screenshot or Screen Recording (max 15 seconds)

📸 Attach screenshot or screen recording showing the updated section (mandatory for all changes).

---

💡 Tech Stack Used:

• HTML / CSS

---

List of File Changed :

no. of file changed :

index.css
index.html
section.css

Uploading Screen Recording 2025-09-07 at 3.03.46 PM.mov…

🔗 Issue Reference:

Closes #IssueNumber 399

---

🧩 Contribution Type:

• Frontend 🎯
• UI/UX 🎨
• Optimization ♻️

---

🙏 Additional Info (if any):

The changes focus on creating a more modern and engaging user interface while maintaining performance. All animations are optimized for smooth performance and include fallbacks for older browsers. The styling is consistent with the platform's design system and improves overall user experience.

Key improvements include:

Better visual hierarchy
Smoother transitions
More consistent spacing
Enhanced mobile responsiveness
Optimized animation performance
Improved accessibility with proper contrast ratios

[vercel]

@Komal-bendresh is attempting to deploy a commit to the vaibhavbabele's projects Team on Vercel.

A member of the Team first needs to authorize it.

[github-actions]

👋 Hi @Komal-bendresh, thank you for opening this Pull Request!
🔧 Please ensure the following:

• ✅ Resolve any merge conflicts, if they exist.make sure you have updated your local repo to avoid conflicts. and solve in your local repo. do not solve in github editor.try to solve in your local repo in vs code or any other editor.
• 🧾 Clearly mention the issue number you are solving (e.g., Fixes #issue_number).
• 📎 Please update your PR description if anything is unclear or incorrect.
• 📷 Attach a screenshot or screen recording of your fix.
• 💬 Kindly share the PR link in the Discord server manually for better tracking.
• if follow the guidelines and fit to project then label according to pr otherwise close the pr.

Happy Contributing! 🚀

[VAIBHAVBABELE]

what you change share screen shot and why it only on index.html file

[Komal-bendresh]

Actually main changes are in index.css file and section.css file .I have changed font size and alignment to sections which were looking like normal paragraphs before and I have added some animations too like on the main page the student is moving with quote and more animations as you scroll the page .

…

On Sun, 7 Sept 2025 at 17:13, Vaibhav Babele ***@***.***> wrote: *VAIBHAVBABELE* left a comment (VAIBHAVBABELE/vaibhavbabele.github.io#420) <#420 (comment)> what you change share screen shot and why it only on index.html file — Reply to this email directly, view it on GitHub <#420 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BJQR5JESXWH3ETDU6Q3PDW33RQK5BAVCNFSM6AAAAACF2XBILKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTENRTG4YTINBYG4> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Preview	Comments	Updated (UTC)
vaibhavbabele-github-io	Ready	Preview	Comment	Sep 7, 2025 6:26pm

[VAIBHAVBABELE]

Disturb the ui of website

[Komal-bendresh]

Sorry I didn’t understand what you meant by disturb the Ui .can you please elaborate 😅

…

On Sun, 7 Sep 2025 at 11:59 PM, Vaibhav Babele ***@***.***> wrote: *VAIBHAVBABELE* left a comment (VAIBHAVBABELE/vaibhavbabele.github.io#420) <#420 (comment)> Disturb the ui of website — Reply to this email directly, view it on GitHub <#420 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BJQR5JC5MS5VIO6SLOI7SCL3RR2RFAVCNFSM6AAAAACF2XBILKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTENRTHE2TQMZVGE> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[github-actions]

⚠️ Merge Conflict Detected!
Hi @Komal-bendresh, your pull request currently has a merge conflict with the base branch. Please resolve the conflict so your PR can be merged.
---
## How to Resolve a Merge Conflict (Step-by-Step)
1. Checkout your PR branch:
bash git checkout frontendOpen

  2. **Fetch the latest changes from the main branch:**
     ```bash
     git fetch origin
     git pull origin main
     ```
  
  3. **Git will show conflict markers in files with conflicts. Open those files, and manually edit them to resolve the differences. Conflict sections look like:**
     ```
     <<<<<<< HEAD
     Your changes
     =======
     Changes from base branch
     >>>>>>> main
     ```
  
  4. **After resolving the conflicts, mark them as resolved:**
     ```bash
     git add <file(s)-you-resolved>
     ```
  
  5. **Commit the resolution:**
     ```bash
     git commit -m "Resolve merge conflict"
     ```
  
  6. **Push your updated branch:**
     ```bash
     git push origin frontendOpen
     ```
  
  ---
  
  🔗 [GitHub Docs: Resolving merge conflicts](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/addressing-merge-conflicts/about-merge-conflicts)
  
  If you need any help, please ask your mentors by replying here!
  
  ---
  
  *This is an automated message to help you resolve merge conflicts and get your PR ready for review. Thank you!*

[Komal-bendresh]

I have fixed the issue.

…

On Mon, 22 Sept 2025 at 18:08, github-actions[bot] ***@***.***> wrote: *github-actions[bot]* left a comment (VAIBHAVBABELE/vaibhavbabele.github.io#420) <#420 (comment)> ⚠️ *Merge Conflict Detected!* Hi @Komal-bendresh <https://github.com/Komal-bendresh>, your pull request currently has a merge conflict with the base branch. Please resolve the conflict so your PR can be merged. --- ## *How to Resolve a Merge Conflict (Step-by-Step)* 1. *Checkout your PR branch:* bash git checkout frontendOpen 2. **Fetch the latest changes from the main branch:** ```bash git fetch origin git pull origin main ``` 3. **Git will show conflict markers in files with conflicts. Open those files, and manually edit them to resolve the differences. Conflict sections look like:** ``` <<<<<<< HEAD Your changes ======= Changes from base branch >>>>>>> main ``` 4. **After resolving the conflicts, mark them as resolved:** ```bash git add <file(s)-you-resolved> ``` 5. **Commit the resolution:** ```bash git commit -m "Resolve merge conflict" ``` 6. **Push your updated branch:** ```bash git push origin frontendOpen ``` --- 🔗 [GitHub Docs: Resolving merge conflicts](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/addressing-merge-conflicts/about-merge-conflicts) If you need any help, please ask your mentors by replying here! --- *This is an automated message to help you resolve merge conflicts and get your PR ready for review. Thank you!* — Reply to this email directly, view it on GitHub <#420 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BJQR5JGBYPGI2B7VUKYHQRL3T7UVFAVCNFSM6AAAAACF2XBILKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTGMJYG43DANZQGQ> . You are receiving this because you were mentioned.Message ID: ***@***.***>