SUCCESSFULLY RE-DESIGN AND ENHANCED THE STAKEHOLDER SECTION #217
+370
−253
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
### SUCCESSFULLY RE-DESIGN AND ENHANCED THE STAKEHOLDER SECTION
solved issue: #209
### 📋 Description
Successfully re-designed and enhanced the stakeholder section of the project. The new design improves the user interface, adds interactive elements, and provides a more professional appearance to the stakeholder cards. This update aims to elevate the visual appeal and functionality of the section, making it more engaging for users while maintaining a clean, responsive layout.
### 🔨 Changes Made
Completely restructured the stakeholder section, introducing a professional card layout for each stakeholder.
Added high-quality images with hover effects and animations to create a more interactive experience.
Implemented responsive design using CSS Grid to ensure the section looks good on all devices, from desktops to mobile.
Introduced a "Read More" button on each card for potential future functionality expansion.
Enhanced typography with modern fonts and a clean, professional look for titles, descriptions, and buttons.
Applied shadow effects and transitions to the cards to make them visually engaging.
✅ ### Checklist
Before submitting the PR, please make sure you have completed the following:
✅ I have followed all the guidelines mentioned in CONTRIBUTING.md.
✅ 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 (if applicable).
✅ I have tested it locally and it works fine.
✅Any dependent changes have been merged and published in downstream modules.
🏷️ ### Types of Changes
What type of changes does your code introduce? (Check all that apply)
[ ]Bug fix (non-breaking change which fixes an issue) 🐛
✅New feature (non-breaking change which adds functionality) ✨
✅ UI enhancement (non-breaking change which enhances UI) 🎨
[ ]Documentation update 📚
Fixes #209
📸 Screenshots (if applicable)
Thank you for contributing to Research Nexus! We look forward to reviewing your PR and getting it merged!