Skip to content

Include "derived status" based on statuses of extensions referenced in the guides metadata - #52100

Open
marko-bekhta wants to merge 2 commits into
quarkusio:mainfrom
marko-bekhta:feat/derived-status
Open

Include "derived status" based on statuses of extensions referenced in the guides metadata#52100
marko-bekhta wants to merge 2 commits into
quarkusio:mainfrom
marko-bekhta:feat/derived-status

Conversation

@marko-bekhta

@marko-bekhta marko-bekhta commented Jan 20, 2026

Copy link
Copy Markdown
Member

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.adoc explicitly.

"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:

image image

The website side of the change:

@quarkus-bot quarkus-bot Bot added area/docstyle issues related for manual docstyle review area/documentation area/infra-automation anything related to CI, bots, etc. that are used to automated our infrastructure labels Jan 20, 2026
@quarkus-bot

quarkus-bot Bot commented Jan 20, 2026

Copy link
Copy Markdown

Status for workflow Quarkus Documentation CI

This is the status report for running Quarkus Documentation CI on commit 6a8907b.

✅ The latest workflow run for the pull request has completed successfully.

It should be safe to merge provided you have a look at the other checks in the summary.

@github-actions

Copy link
Copy Markdown

🎊 PR Preview a65afc6 has been successfully built and deployed to https://quarkus-pr-main-52100-preview.surge.sh/version/main/guides/

  • Images of blog posts older than 3 months are not available.
  • Newsletters older than 3 months are not available.

@FroMage FroMage left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

So we move all statuses out of the guides and pull from metadata? Great!

@gsmet gsmet left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

@cescoffier

Copy link
Copy Markdown
Member

This is a very good idea.

@gsmet does this "conflict" with your new structure?

@cescoffier

Copy link
Copy Markdown
Member

What's the status on this one?

@FroMage

FroMage commented May 26, 2026

Copy link
Copy Markdown
Member

I thought this was merged years ago 😱

@cescoffier

Copy link
Copy Markdown
Member

It needs to be rebased.

@marko-bekhta

Copy link
Copy Markdown
Member Author

hey 👋🏻 🙂

yeah 😖, this one is still on my todo list. I think we have a better chance of integrating it after we are finished with

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area/docstyle issues related for manual docstyle review area/documentation area/infra-automation anything related to CI, bots, etc. that are used to automated our infrastructure

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants