Update FAQ with links to extensions.quarkus.io and syntax updates #2168
Conversation
holly-cummins
force-pushed
the
improve-faq
branch
from
2c9a9a9 to
91e1c06
Compare
|
🙈 The PR is closed and the preview is expired. |
|
Preview link: https://quarkus-site-pr-2168-preview.surge.sh/faq/ |
faq.adoc
Outdated
| Yes, we consider Quarkus stable. | ||
| Quarkus is used in production by a https://quarkus.io/blog/tag/user-story/[range of organisations]. | ||
| Remember 95% of the features Quarkus apps use are provided by the ecosystem like Hibernate ORM, Eclipse Vert.x, Netty, RESTEasy, etc. These libraries are rock solid :) |
There was a problem hiding this comment.
I'm not sure about this content now tbh but probably not something to discuss in this PR.
I wonder if I would have wide range of organizations (see some link:user stories) because otherwise it's a bit limiting. But not really sure and also don't want to start a long discussion here.
There was a problem hiding this comment.
Yeah, I decided to go for "make it better than it currently is" rather than "make it optimal". I agree a bigger rewrite is needed.
There was a problem hiding this comment.
I don't have strong feelings about either wording, so I've gone with your suggestion and squashed.
holly-cummins
force-pushed
the
improve-faq
branch
from
a0f0203 to
0de018f
Compare
|
Could I nudge on this? I've got another change backed up behind it ... |
…k to user stories, use adoc-style headings Also replace link to old extensions page with a better link to code.quarkus.io Co-Authored-By: Guillaume Smet <[email protected]>
|
Sorry, missed your ping, I fixed the conflict for you because the issue came from me lagging. I'll merge once CI is green. |
|
Thanks! |
I was trying to google for the maturity matrix, but it's not indexed yet. What google did send me to was the general FAQ, which has a line about how we have a maturity model, and no link. There couldn't be a link because the reference is several years old. I can't add a link until the matrix doc is in a 'latest' release, but while I was looking at the doc, I noticed a few other areas that could use some love.
There's a suggestion to use code.quarkus.io to check extension status, but extensions.quarkus.io is a more natural place to look up that kind of metadata. It also assumes no extensions live in the quarkiverse org, presumably because it was written before there was one.
The wording about stability is a bit weak, so I strengthened with a link to our user stories.
I also noticed the headings were markdown ones, so I swapped them to adoc style.
Finally, there was a link to the 'orginal' /extensions page, which now redirects to code.quarkus.io. For that link, code.quarkus.io is a much better destination, so I've replaced /extensions with code.quarkus.io.