Include "derived status" based on statuses of extensions referenced in the guides metadata#52100
Include "derived status" based on statuses of extensions referenced in the guides metadata#52100marko-bekhta wants to merge 2 commits into
Conversation
…n the guides metadata
as now that would be autogenerated
Status for workflow
|
|
🎊 PR Preview a65afc6 has been successfully built and deployed to https://quarkus-pr-main-52100-preview.surge.sh/version/main/guides/
|
FroMage
left a comment
There was a problem hiding this comment.
So we move all statuses out of the guides and pull from metadata? Great!
gsmet
left a comment
There was a problem hiding this comment.
I think it's a great idea and we should definitely pursue it.
But I would like us to figure out how to handle the other side of things before we merge this one: quarkusio/quarkusio.github.io#2519 (review) , as there might be some work needed for the metadata.
|
This is a very good idea. @gsmet does this "conflict" with your new structure? |
|
What's the status on this one? |
|
I thought this was merged years ago 😱 |

Hi 👋🏻 🙂
this is a followup on
with the idea being that we may not necessarily have extension statuses listed in the adoc guides. this patch reads the statuses from the built extensions and generates an include file with extension statuses.
Then on the quarkus.io side there's an asciidoc extension that checks for an explicitly specified status in the guide, and fallsback to the extension statuses (from the include file) to "automatically" insert a status label + explanation text, so with that there's no need to include the
extension-status.adocexplicitly."derived" status is also included in the yaml, so that search.quarkus.io could include that info in the index and use in search results.
The way it would look:
The website side of the change: