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

[Bug] Footer uses Twitter logo instead of Bluesky logo #315

Open
1 task done
SumaiyaaRq opened this issue Nov 20, 2024 · 3 comments · May be fixed by #318
Open
1 task done

[Bug] Footer uses Twitter logo instead of Bluesky logo #315

SumaiyaaRq opened this issue Nov 20, 2024 · 3 comments · May be fixed by #318
Labels
💻 aspect: code Concerns the software code in the repository 🛠 goal: fix Bug fix 🟧 priority: high Stalls work on the project or its dependents 🏁 status: ready for work Ready for work

Comments

@SumaiyaaRq
Copy link
Contributor

Description

The footer currently displays the Twitter logo in the social-menu . According to the new design system, the social-menu should contain the Bluesky logo and not the Twitter logo in the footer region . This discrepancy may cause confusion and needs to be updated for consistency with the new design guidelines.

Reproduction

  1. Open the website .
  2. Navigate to the footer region .
  3. Observe the logos in the footer section.
  4. See error.

Expectation

The footer should display the Bluesky logo instead of the Twitter logo. Updating the footer to reflect this change will ensure alignment with the design guidelines and avoid user confusion.

Screenshots

Actual social-menu :
Screenshot 2024-11-20 at 11 56 24 PM

social-menu according to Vocabulary Design System :
Screenshot 2024-11-20 at 11 57 39 PM

Environment

  • Device: (Laptop)
  • OS: (macOS)
  • Browser: (Chrome)

Additional context

https://github.com/creativecommons/vocabulary/blob/3633bb1f6e982b42575309558e6aaa3ddf906d8b/docs/index.html#L354-L362

Resolution

  • I would be interested in resolving this bug.
@SumaiyaaRq SumaiyaaRq added 💻 aspect: code Concerns the software code in the repository 🚦 status: awaiting triage Has not been triaged & therefore, not ready for work 🛠 goal: fix Bug fix 🟧 priority: high Stalls work on the project or its dependents labels Nov 20, 2024
@cc-open-source-bot cc-open-source-bot moved this to Triage in WebDev Nov 20, 2024
@possumbilities possumbilities moved this from Triage to Backlog in WebDev Nov 22, 2024
@possumbilities possumbilities added 🏁 status: ready for work Ready for work and removed 🚦 status: awaiting triage Has not been triaged & therefore, not ready for work labels Nov 22, 2024
@SumaiyaaRq
Copy link
Contributor Author

Hi @possumbilities , I am currently working on this issue (#315) , and while implementing the solution, I realised that the necessary changes require modifications to some upstream files . I’ve made some progress, and the icon starts appearing after modifying the files style.css & index.html . However, to ensure the icon is displayed correctly and functions as intended, I need to add a path to the fa-icons.svg file located in the upstream Vocabulary folder.

In a previous contribution, I was advised not to modify files in the upstream folder. I want to confirm if this guideline still applies here or if an exception can be made in this case. Alternatively, if there’s a specific approach you’d like me to follow , I’d appreciate your guidance.

Thank you for your support!

@possumbilities
Copy link
Contributor

possumbilities commented Nov 25, 2024

@SumaiyaaRq The correct course here would be to add the most current versions of the library-vars.css and fa-icons.svg files from the upstream Vocabulary repository to this repository's Vocabulary.

for similar, see:

@SumaiyaaRq
Copy link
Contributor Author

@possumbilities Thank you for the guidance !

@SumaiyaaRq SumaiyaaRq linked a pull request Nov 26, 2024 that will close this issue
7 tasks
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 🛠 goal: fix Bug fix 🟧 priority: high Stalls work on the project or its dependents 🏁 status: ready for work Ready for work
Projects
Status: Backlog
Development

Successfully merging a pull request may close this issue.

2 participants