You don't understand what I'm talking about.
I understand perfectly well what open source is, I have been dealing with it for 14 years. Including, sometimes I do something of my own. But if my product is not intended to be used according to the instructions for what it is based on, I write about it in big red letters so that people do not waste time on actions that are not designed for results. Is Orange Pi shamelessly stealing from Armbian? Apparently, they still came up with the phrase “the flashing manual is intended only for our images”, which helps save time without making unnecessary mistakes. And they have (not so fancy but) manual, by the way.
What I am asking from you is not some kind of feat, or a "fancy manual", or something for which you need to involve PR. We are talking about the basic required minimum: if you want to attract people to your project, it must be attractive. At a minimum, attract by accessibility of use.
It should at least run.
If it not designed to be run using certain methods, (RkDevTool for example) just write one sentence about it right above the download link. If you suddenly have some kind of documentation, attach a link to it there. There's nothing complicated about it, no one forces you to write archwiki for each image.
You can’t just do it "somehow", post it without the simplest explanation and justify it by saying that it’s open source. All Linux is open-source, and 99% of them either just work, or without a forum it’s clear how to make them work.
Because it's just minimum.