Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remove 'Reactive' as a category for docs #33992

Merged
merged 1 commit into from
Jun 13, 2023

Conversation

michelle-purcell
Copy link
Contributor

Fixes this problem:
On the Quarkus doc landing page, when you filter the guides by selecting the "Reactive" category, zero results display.
This is because none of the guides use the categories: reactive attribute.

Solution
Remove the reactive category from the current doc taxonomy.

Context

In PR #33486 @cescoffier concluded that we should remove this category from the docs filter list, as per the following rationale:

image

@michelle-purcell
Copy link
Contributor Author

@cescoffier - FYI.
@gsmet / @ebullient - Please review this doc config modification and merge if you approve.

Copy link
Member

Choose a reason for hiding this comment

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

You may hit a conflict w/ this file and the other PR, as I'm seeing similar changes. I think the only one you intend here is removal of like 395 (removing reactive from table)

@github-actions
Copy link

github-actions bot commented Jun 12, 2023

🙈 The PR is closed and the preview is expired.

@quarkus-bot
Copy link

quarkus-bot bot commented Jun 12, 2023

✔️ 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.

@ebullient ebullient merged commit c837ba5 into quarkusio:main Jun 13, 2023
@quarkus-bot quarkus-bot bot added this to the 3.2 - main milestone Jun 13, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants