Marxon Thanks for sharing feedback and great that you like it!
Many thanks for your offer on translation.
For now, I would suggest sticking to English only for now. give. Maintaining multiple languages by such a small team seems always be challenging…
If the overall community sees benefit, I am happy to revisit it. I am just hesitant to proactively start this, if there is no obvious demand.
…but maybe you would like to support creating some documentation which is currently missing?
Are you adding the effects api later, too?
Are you talking about https://docs.hyperion-project.org/effects/API.html?
In case yes, this one should not be added to the integration API.
Looks like the term API is misleading here.
I suggest changing the wording to „Effect Development Framework“ which would more clearly address that it is a toolkit for custom effect development and not an interface to Hyperion.
If you were referring to something else, please shout.