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

Update favicon #29

Merged
merged 2 commits into from
Nov 27, 2024
Merged

Update favicon #29

merged 2 commits into from
Nov 27, 2024

Conversation

glenn-jocher
Copy link
Member

@glenn-jocher glenn-jocher commented Nov 27, 2024 β€’

πŸ› οΈ PR Summary

Made with ❀️ by Ultralytics Actions

🌟 Summary

Updated the website's favicon to a new hosted file for better maintainability and branding. ✨

πŸ“Š Key Changes

  • Removed the local favicon.ico file from the repository.
  • Updated the mkdocs.yml configuration to reference a new favicon hosted online: favicon-yolo.png.

🎯 Purpose & Impact

  • πŸ“ Improved maintainability: By using a hosted favicon, future updates can be managed directly via the hosted URL without modifying the codebase.
  • 🎨 Consistent branding: The new favicon aligns with the YOLO branding, enhancing the user experience and brand identity on the documentation site.
  • πŸš€ Simplified repository: Removing the local favicon file reduces clutter in the codebase.

Copy link

vercel bot commented Nov 27, 2024 β€’

The latest updates on your projects. Learn more about Vercel for Git β†—οΈŽ

Name Status Preview Comments Updated (UTC)
handbook βœ… Ready (Inspect) Visit Preview πŸ’¬ Add feedback Nov 27, 2024 11:32am

@UltralyticsAssistant UltralyticsAssistant added documentation Improvements or additions to documentation enhancement New feature or request labels Nov 27, 2024
@UltralyticsAssistant
Copy link
Member

πŸ‘‹ Hello @glenn-jocher, thank you for submitting an ultralytics/handbook πŸš€ PR! To ensure a seamless integration of your work, please review the following checklist:

  • βœ… Define a Purpose: Clearly explain the purpose of your fix or feature in your PR description, and link to any relevant issues. Ensure your commit messages are clear, concise, and adhere to the project's conventions.
  • βœ… Synchronize with Source: Confirm your PR is synchronized with the ultralytics/handbook main branch. If it's behind, update it by clicking the 'Update branch' button or by running git pull and git merge main locally.
  • βœ… Ensure CI Checks Pass: Verify all Ultralytics Continuous Integration (CI) checks are passing. If any checks fail, please address the issues.
  • βœ… Update Documentation: Update the relevant documentation for any new or modified features.
  • βœ… Add Tests: If applicable, include or update tests to cover your changes, and confirm that all tests are passing.
  • βœ… Sign the CLA: Please ensure you have signed our Contributor License Agreement if this is your first Ultralytics PR by writing "I have read the CLA Document and I sign the CLA" in a new message.
  • βœ… Minimize Changes: Limit your changes to the minimum necessary for your feature addition or update. "It is not daily increase but daily decrease, hack away the unessential. The closer to the source, the less wastage there is." β€” Bruce Lee

For more guidance, please refer to our Contributing Guide. πŸš€

This is an automated response πŸ“’, but please rest assured that an Ultralytics engineer will review your PR soon to provide additional feedback or merge it. If you have any questions, leave a comment here and we'll be happy to help!

Thank you for improving the ultralytics/handbook user experience and keeping the code clean and modern! 🎨✨

@glenn-jocher glenn-jocher merged commit bbe050d into main Nov 27, 2024
2 of 3 checks passed
@glenn-jocher glenn-jocher deleted the fav branch November 27, 2024 11:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation enhancement New feature or request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants