-
Notifications
You must be signed in to change notification settings - Fork 3k
Restructure native executable guide for better accessibility #49553
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
base: main
Are you sure you want to change the base?
Restructure native executable guide for better accessibility #49553
Conversation
KohiiTM
commented
Aug 15, 2025
- Lead with container-based builds requiring only Docker/Podman
- Move intimidating prerequisites (C development environment) to later section
- Keep initial prerequisites short and focused
- Reorganize content to be more beginner-friendly while preserving all technical details
- Lead with container-based builds requiring only Docker/Podman - Move intimidating prerequisites (C development environment) to later section - Keep initial prerequisites short and focused - Reorganize content to be more beginner-friendly while preserving all technical details Fixes quarkusio#49398
This comment has been minimized.
This comment has been minimized.
🎊 PR Preview 6800f94 has been successfully built and deployed to https://quarkus-pr-main-49553-preview.surge.sh/version/main/guides/
|
@KohiiTM I like the part where you push the builder image option first, but IMHO it needs an explanation right off the bat that one needs a native-image tool that comes e.g. with GraalVM or Mandrel and that the tool could be either in a builder image or downloaded and installed on your OS just like a JDK. ![]() |
@Karm Thank you for the feedback. I appreciate you taking the time to review it. I agree with your suggestion to add an explanation about the need for a native-image tool right at the beginning. Regarding your question about better accessibility, my goal was to make the documentation less intimidating for new users. I thought that by leading with a simpler, container-based approach, it would feel more approachable since it has fewer upfront prerequisites. My commit wording can definitely be changed to be more specific. |
- Lead with container-based builds requiring only Docker/Podman - Move intimidating prerequisites (C development environment) to later section - Keep initial prerequisites short and focused - Reorganize content to be more beginner-friendly while preserving all technical details Fixes quarkusio#49398
54cee2e
to
c9132ac
Compare
Ignore; I have not made any changes yet. |
This comment has been minimized.
This comment has been minimized.
…thub.com/KohiiTM/quarkus into docs/restructure-native-executable-guide
Add explanation of what the native-image tool is and how it can be obtained (locally via GraalVM/Mandrel or through container images) in the Prerequisites section to address feedback that users need conceptual understanding before jumping into implementation steps. Fixes quarkusio#49398
Status for workflow
|