support for common emojione CDNs
rriemann opened this issue · 5 comments
Hello,
currently, the configured asset path is always suffixed by /emoji/unicode/.
However, many CDNs do not have such a path suffix, e.g.
https://cdn.jsdelivr.net/emojione/assets/3.0/png/32/1f600.png
Please allow for a more powerfull configuration of the asset location, so that I can use emojione or emojitwo.
Best,
Robert
This issue has been automatically marked as stale because it has not been commented on for at least two months.
The resources of the Jekyll team are limited, and so we are asking for your help.
If this is a bug and you can still reproduce this error on the master branch, please reply with all of the information you have about it in order to keep the issue open.
If this is a feature request, please consider whether it can be accomplished in another way. If it cannot, please elaborate on why it is core to this project and why you feel more than 80% of users would find this beneficial.
This issue will automatically be closed in two months if no further activity occurs. Thank you for all your contributions.
I guess it requires to add a configuration option for a prefix string.
This issue has been automatically marked as stale because it has not been commented on for at least two months.
The resources of the Jekyll team are limited, and so we are asking for your help.
If this is a bug and you can still reproduce this error on the master branch, please reply with all of the information you have about it in order to keep the issue open.
If this is a feature request, please consider whether it can be accomplished in another way. If it cannot, please elaborate on why it is core to this project and why you feel more than 80% of users would find this beneficial.
This issue will automatically be closed in two months if no further activity occurs. Thank you for all your contributions.
This is still an important issue. This gem introduces dependencies to Github CDN that are otherwise difficult to replace.
I see that the Jekyll team resources are limited and this fact is maybe best reflected by keeping open issues open.
I see that the Jekyll team resources are limited and this fact is maybe best reflected by keeping open issues open.
This seems like a low priority, and nobody has stepped forward with a PR. Closing for now.