Quarkus: Improve Extension Author Guide

[ebramirez]

This is a request to improve the Extension Author Guide.

The current documentation is pretty impressive but completely inaccessible for the uninitiated like me.

A real life example would be of tremendous help. For example, I would like to create a Quarkus extension for Vaadin, which looks like a rewrite of the project Vaadin CDI, but I don't know where to start.

The ideal examples would have several blocks like: "Look for THIS (Example of initialization, instrumentation, etc) which translates into THAT (equivalent operation in Quarkus)".

Hope this makes sense.

[ebramirez]

It looks like @manovotn had similar thoughts in #1690.

[starksm64]

The guide has been significantly expanded in the 0.13 release, so what feedback do you have on that relative to this issue?

https://quarkus.io/guides/extension-authors-guide

[ebramirez]

The guide has been significantly expanded in the 0.13 release, so what feedback do you have on that relative to this issue?

You are right that the docs have improved, but still, an example of how to write an extension from scratch would be fantastic.

[danielpetisme]

As discussed on Zulip, I'll work on this one.

[Dufgui]

it's maybe a duplicate of #2277 now no ? or is there any still some improvement missing ?
@danielpetisme @ebramirez

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you!
We are doing this automatically to ensure out-of-date issues does not stay around indefinitely.
If you believe this issue is still relevant please put a comment on it on why and if it truly needs to stay request or add 'pinned' label.

[gsmet]

Closing as duplicate of https://github.com/quarkusio/quarkus/issues/2277 .