Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature] Enhance User Experience with Box Shadow on Hover in Featured Posts Section #821

Open
1 task done
Dev-JoyA opened this issue Oct 6, 2024 · 6 comments
Open
1 task done
Labels
💻 aspect: code Concerns the software code in the repository 🕹 aspect: interface Concerns end-users' experience with the software ✨ goal: improvement Improvement to an existing feature 🟩 priority: low Low priority and doesn't need to be rushed 🚧 status: blocked Blocked & therefore, not ready for work

Comments

@Dev-JoyA
Copy link
Contributor

Dev-JoyA commented Oct 6, 2024

Problem

The featured posts section feels static and doesn’t engage users effectively.

Description

By adding a box shadow effect when users hover over the posts, we can make it more visually appealing and interactive. This change will help draw attention to the featured content and encourage users to explore it further, ultimately improving the user experience.

Implementation

  • I would be interested in implementing this feature.
@Dev-JoyA Dev-JoyA added ✨ goal: improvement Improvement to an existing feature 💻 aspect: code Concerns the software code in the repository 🚦 status: awaiting triage Has not been triaged & therefore, not ready for work 🟩 priority: low Low priority and doesn't need to be rushed labels Oct 6, 2024
@cc-open-source-bot cc-open-source-bot moved this to Triage in TimidRobot Oct 6, 2024
@nazarenegena

This comment was marked as outdated.

@Dev-JoyA

This comment was marked as outdated.

@nazarenegena

This comment was marked as outdated.

@TimidRobot TimidRobot added 🚧 status: blocked Blocked & therefore, not ready for work 🕹 aspect: interface Concerns end-users' experience with the software and removed 🚦 status: awaiting triage Has not been triaged & therefore, not ready for work labels Oct 7, 2024
@TimidRobot TimidRobot moved this from Triage to Backlog in TimidRobot Oct 7, 2024
@TimidRobot TimidRobot moved this to Backlog in possumbilities Oct 7, 2024
@TimidRobot
Copy link
Member

Please see Contribution Guidelines — Creative Commons Open Source for how we manage issues and pull requests (PRs).

We generally don't assign issues prior to resolution. Instead of asking for issues to be assigned, do the work and submit a PR. Even if multiple people submit PRs for the same issue, multiple ideas and implementations strengthen the final product.

For work program applicants, each can all list their own PRs on their application. It is the quality of work that is important, not whether it is merged.

@TimidRobot
Copy link
Member

🚧 status: blocked Blocked & therefore, not ready for work :

This UX feature should be first discussed as part of the Vocabulary design system:

@Prince-Tagadiya

This comment was marked as off-topic.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
💻 aspect: code Concerns the software code in the repository 🕹 aspect: interface Concerns end-users' experience with the software ✨ goal: improvement Improvement to an existing feature 🟩 priority: low Low priority and doesn't need to be rushed 🚧 status: blocked Blocked & therefore, not ready for work
Projects
Status: Backlog
Status: Backlog
Development

No branches or pull requests

4 participants