MKS-Klipad50: Switch to standard support

[torte71]

Switch MKS-Klipad50 to standard support.

Do I need to update https://www.armbian.com/update-data/ again?
I have added my data already about 3 weeks ago on the initial import.

[igorpecovnik]

Do I need to update

No, just once. If relation to this board is already there, then this is it.

[igorpecovnik]

BTW: website status is still at manual change.

[torte71]

BTW: website status is still at manual change.

Sorry, but I don't get what you mean.
Do I have to change anything? (I saw the support selection box in the device wordpress template can be set to standard support)
Or does it just mean that until the release the Armbian pages won't be updated?

[igorpecovnik]

Do I have to change anything? (I saw the support selection box in the device wordpress template can be set to standard support)

This, yes, optionally. If (most of) conditions applies: https://docs.armbian.com/User-Guide_Board-Support-Rules/#standard-support

Or does it just mean that until the release the Armbian pages won't be updated?

It can be done now. Website is not fully automatized ... we will probably ditch it and make it from scratch one day.

[torte71]

I still don't understand, what you are referring to (and if or what actions I or you need to take).

I changed the support type in the wordpress template to "standard" and now it gets listed below standard support on https://www.armbian.com/download - just as expected.
The image files on https://www.armbian.com/mks-klipad50/ still refer to the community builds, but I thought that is because the images at https://github.com/armbian/os/ have not been rebuilt yet (since klipad was changed from .csc to .conf).

Your comments look to me, as if there are still additional steps required for a "manual change" of the "website status", but I have no idea, what these steps could be and what they will change.

[torte71]

Did you refer to the "Build Standard Support Images" workflow being triggered manually?
Then yes, it would be nice if this would be run for the mksklipad50.

(I somehow overlooked that this workflow is not triggered automatically and focused only on finding another kind of automatism where "status is at manual change" could apply.)