You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The development of Kirby 4 is getting along and there finally will be a core color field. It works differently in some parts, yes, but it does what you'd expect from a color field. So the question is: Are there parts that the core will not offer that are widely required that justify continued work on the plugin?
For our studio, checking contrast is the essential part but this could be done via a separate field.
So, if you have been using this field could you please react to this issue with a:
👎 for discontinuing the plugin
👍 for keeping this plugin
If you vote for updating this plugin, please add a comment what you are using the field for that the core does not offer. Thanks ❤️
The text was updated successfully, but these errors were encountered:
nilshoerrmann
changed the title
Kirby 4: deprecate this plugin?
Kirby 4: discontinue this plugin?
Sep 28, 2023
Maintaining a PHP port of APCA-W3 seems like a nightmare because of their wild license requirements to follow suit any update to their core algorithm. Also their naming (or not naming) requirements are complicated. That's why we stepped back from adding APCA to this plugin so far. But it might be an idea to rely on an external library for this. Colori might be interesting: https://github.com/Remiscan/colori
As I wrote above, we are very much interested in keeping contrast checks available as plugin. And converting and manipulating colors fits in there as well.
The development of Kirby 4 is getting along and there finally will be a core color field. It works differently in some parts, yes, but it does what you'd expect from a color field. So the question is: Are there parts that the core will not offer that are widely required that justify continued work on the plugin?
For our studio, checking contrast is the essential part but this could be done via a separate field.
So, if you have been using this field could you please react to this issue with a:
If you vote for updating this plugin, please add a comment what you are using the field for that the core does not offer.
Thanks ❤️
The text was updated successfully, but these errors were encountered: