Improved favicon support

[TysonMN]

If the user provides a path to a favicon in the config...

codedoc/samples/config.ts

Lines 21 to 23 in 88d00db

	page: {
	favicon: '/favicon.ico',
	},

...then CODEDOC adds the following link element...

codedoc/src/components/page/index.tsx

Line 40 in cdb1b59

{options.favicon ? <link rel="shortcut icon" href={options.favicon}/> : ''}

...to the head element.

A web programmer friend of mine recommended RealFaviconGenerator. Maybe there are a hundred sites like this; I am still new to this.

For what it's worth though, RealFaviconGenerator thinks there are many opportunities for codedoc.cc to improve its use of favicons. Here is the report.

Given a master image (with size 260x260 or more), these instructions show how to use the npm package cli-real-favicon to generate all the various image files and then modify any HTML to correctly reference those images.

Is there any desire for CODEDOC to take this on as a dependency to step up its favicon game?

Or would it be more appropriate to make a plugin for CODEDOC that utilizes ReadFaviconGenerator?

[loreanvictor]

There is one particular error in the report pertaining to icon of pinned tabs on Safari. Safari however seems to have no problem with pinning codedoc.cc.

Besides that, the rest of the issues are about the resolution of the icon when you add it to your home screen. Since this is not the typical usage for websites generated by CODEDOC, I would say it falls out of core functionality and would be better suited for a plugin.

[TysonMN]

Oh, RealFaviconGenerator doesn't seem like such a good choice to me anymore. Its GitHub repo only has two commits from seven years ago.

[TysonMN]

Humm...that was only one of the repos in that GitHub organization. Other repos were updated more recently.