Favicon for docs?
See original GitHub issueHi, first of all, thanks for this project!
It would be nice to have a favicon to identify the tabs when no titles are shown (see screenshot below). It looks like the docs are being built with gx
, but I didn’t see on first glance where a PR would be made for a favicon.
Maybe an option would be a monochrome / adapted version of the logo image?
Issue Analytics
- State:
- Created 4 years ago
- Comments:5 (2 by maintainers)
Top Results From Across the Web
Favicon - MDN Web Docs Glossary: Definitions of Web-related ...
A favicon (favorite icon) is a tiny icon included along with a website, which is displayed in places like the browser's address bar, ......
Read more >Define Website Favicon for Search Results - Google Developers
Google Favicon is the user agent for downloading favicons defined by websites. It is a low-volume crawler: it may visit the homepage of...
Read more >FavIdenticon for Google Docs
This extension gives each Docs, Sheets, and Slides document a unique favicon to make them visually distinguishable in a long row of small ......
Read more >How can I get a specific favicon for my docs? - Google Support
I don't believe there is any way to add a unique favicon to Docs documents or sheets. However, if you have an identifying...
Read more >Setting a Custom Favicon - HelpDocs Support
Uploading a Custom Favicon · Go to Settings > Brand · Find the Favicon image dropzone, and click to upload your image (or...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Ok this sounds like a plan. I took a look through the project (I’ve filed this issue in the wrong repo) and found the files that will be probably interesting to me (really cool that React components are the single source of truth here too!).
I’ve documented these decisions in rebassjs/rebassjs.org#15. Closing this.
This was done in https://github.com/rebassjs/rebass/commit/1a46adb7fb184276dcf854b939ce1813ec3a9241