Hybrid "root + sub-directory" setting

[phbernard]

Currently, the user can choose two locations for his icons:

• The root directory (recommended solution). Problem: it's a mess. Clearly.
• A sub-directory. Problem: annoying 404 regarding favicon.ico, Yandex won't find favicon.ico, etc.

There could be a third, hybrid solution: everything in a sub-directory, except for favicon.ico. And maybe more files: browserconfig.xml, apple-touch-icon.png... But not too much, else the benefits of this approach are lost.

Yet, this approach as some drawbacks:

• The benefits are not obvious for the newcomer. Not everyone want to read the FAQ to understand all the aspects of the "root/not" root issue. So a third option might sound like complex stuff.
• The installation procedure is more difficult. Copy this here, copy that there...

[dandv]

After ~half an hour with RFG, I was going to suggest the same approach:

• root: favicon.ico, browserconfig.xml, manifest.json (used later to build a PWA)
• /icons/: *.png, safari-pinned-tab.svg

I'm using this approach in production and it works almost flawlessly (the last warning is because GitHub pages serves the site under a subdirectory),

The installation procedure is more difficult. Copy this here, copy that there...

Solution: RFG can output a ZIP archive with the /icons/ subdirectory inside, as described above. Then the user only have to unzip it in the root folder.

Best of both worlds.

Not everyone want to read the FAQ to understand all the aspects of the "root/not" root issue. So a third option might sound like complex stuff.

Just offer that as the default, recommended option.

[filips123]

Is there any update? I agree with @dandv and I also use this on my websites.