DTS supported platforms and workflows generation
The problem you're addressing (if any)
Current DTS section in docs.dasharo.com gets outdated quickly. And updating it is a headache.
Describe the solution you'd like
Maybe we could use the metadata from dts-configs to generate the documentation (note, that we have not migrated all needed metadata from meta-dts yet)? Furthermore I think we should generate a some kind of matrix, to display supported workflows per supported hardware more clearly. As now some platforms support transition to Dasharo (coreboot+SeaBIOS) and some do not.
Where is the value to a user, and who might that user be?
Easier maintenance of the documentation. Better user experience.
Describe alternatives you've considered
No response
Additional context
W will need to add an additional JSON to the dts-configs repository that will map the dmidecode strings from the dts-configs/configs/*.json to the platforms from Supported hardware page. But we will have to hardcode the supported hardware strings to the added JSON. Maybe we can get the list from Dasharo/docs and not hardcode it?
@DaniilKl can i work on this ?
@MAVRICK-1, yes, of course, let me know if you need more information here.
But we will have to hardcode the supported hardware strings to the added JSON. Maybe we can get the list from Dasharo/docs and not hardcode it?
@MAVRICK-1, do you have any ideas?
Maybe we can get the list from Dasharo/docs and not hardcode it?
It seems to me the tradeoff (maintenance cost) is too big to make automating this reasonable. I totally get why you would like to have something like that, yet I think this could be resolved with adding yet another point to "Release TO-DO list". It is not automatic, but reliable... If it does not exist, it can't break, which might be important when the release is running late.
@DaniilKl @macpijan Let me know what you think.