FAQ (frequently asked questions) documentation for extensions

[holly-cummins]

This combines the

• A list of FAQs
• List of common extension tasks (dev service, rewrite byte code, etc) with links to a “how to”, indexed by the ‘problem being solved’ rather than the ’solution technology’

goals from #37288.

FAQ for the FAQ :) 



Uh, Holly, it doesn't build cleanly

It's waiting for #42446 to merge. If we think that PR will be a long time I'll remove the cross-references to un-block this PR, but they fit in quite nicely so it would be nice to not have to redo them. #42446 has not been merged yet, but references to #42446 have been removed, in the hopes of allowing forward progress.

Is this complete?

Goodness me, no! But has been open for ages, so I decided not to let perfect be the enemy of good. Once we have a FAQ, we can iterate.

Is the Diataxis type right?

I wondered about this too, and consulted with @ebullient. We decided that this document is a pointer to other how-tos, and it’s ok that it itself doesn’t fit exactly into one of the diataxis types.

Is the JobRunr link the right one?

I wasn’t sure whether to link to the JobRunr repo or the extensions page. Normally the extensions page would link to the repo, but for JobRunr it doesn’t. I’ve raised an issue to try and get that sorted out, so decided to go for the ‘long term best’ link.

[quarkus-bot]

Thanks for your pull request!

Your pull request does not follow our editorial rules. Could you have a look?

• title should preferably start with an uppercase character (if it makes sense!)

_{This message is automatically generated by a bot.}

[holly-cummins]

@maxandersen and @gsmet, do you have a sense whether this PR or #42446 is likely to merge first? I assumed when I did the cross-references that they'd merge in the order I submitted them – but if we think this is will merge before #42446 I'll remove the cross-reference so that this compiles cleanly and is merge-able without being blocked on #42446.

[holly-cummins]

As there's no immediate prospect of #42446 merging, I don't think this PR should block on that content. I've removed The xref:extension-maturity-model[extension maturity model] shows the kinds of capabilities extensions can offer. from line 22, and changed 'Another useful thing' to 'One useful thing' on the following line.

There's also a whole section that I've removed:

## How do I know what kind of capabilities I might want to include in an extension?

Have a look at the xref:extension-maturity-model[extension maturity model].

[github-actions]

🎊 PR Preview 0545457 has been successfully built and deployed to https://quarkus-pr-main-42520-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.

[quarkus-bot]

Status for workflow Quarkus Documentation CI

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

✅ 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.