Swap code.quarkus and github links for extensions.quarkus.io, add link to user stories, use adoc-style headings

Author: holly-cummins

faq.adoc

@@ -15,9 +15,11 @@ Quarkus is published in Maven Central, check out link:/extensions[which extensio
 
 == Quarkus is stable?
 
-Yes, we consider Quarkus stable. 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 :)
+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 :)
 
-You can go to https://code.quarkus.io/[code.quarkus.io] to see if a particular extension is _stable_ (default) or _preview_.
+You can go to https://quarkus.io/extensions[quarkus.io/extensions] to see if a particular extension is _stable_ (default) or _preview_.
 
 == What is a Quarkus extension?
 
@@ -37,7 +39,7 @@ Extensions have a various degree of maturity when they enter the Quarkus ecosyst
 
 *Deprecated*: backward compatibility and presence in the ecosystem is not guaranteed. Such extensions are likely to be replaced or removed in a future version of Quarkus.
 
-You can find the extension status on https://code.quarkus.io[code.quarkus.io] or in the extension link:/guides/[guides].
+You can find the extension status on https://quarkus.io/extensions[quarkus.io/extensions] or in the extension link:/guides/[guides].
 
 == Can I write an extension?
 
@@ -47,27 +49,27 @@ Oh yeah! We had quite a few extensions written outside the Quarkus "initial" tea
 
 Quarkus is an open ecosystem and we hope to see all the extensions people need to write their apps. We are working as we speak to allow an extension to be published in separate repos and separate GAVs and thus published in Maven repos independently of Quarkus core. This will greatly simplify the publication process. Expect news soon.
 
-The one current restriction is that extensions should work in both OpenJDK and GraalVM native executables. That is the guarantee we give Quarkus users (a cross compilation for their app). We have a maturity model to improve an extension to be fully "Quarked" and benefit from Quarkus, all done in incremental steps. Just hop on our https://quarkus.io/community/#discussions[mailing list] to discuss your ideas and get help. And you can start reading our https://quarkus.io/guides/writing-extensions[Writing extensions guide] as well or more simply get inspiration from the https://github.com/quarkusio/quarkus/tree/main/extensions[existing ones].
+The one current restriction is that extensions should work in both OpenJDK and GraalVM native executables. That is the guarantee we give Quarkus users (a cross compilation for their app). We have a maturity model to improve an extension to be fully "Quarked" and benefit from Quarkus, all done in incremental steps. Just hop on our https://quarkus.io/community/#discussions[mailing list] to discuss your ideas and get help. And you can start reading our https://quarkus.io/guides/writing-extensions[Writing extensions guide] as well or more simply get inspiration from the https://quarkus.io/extensions[existing ones].
 
 
-## What is GraalVM?
+== What is GraalVM?
 
 https://www.graalvm.org[GraalVM] is a universal virtual machine for running applications written in various different languages, as well as providing the ability to compile JVM bytecode to a native executable (this native executable runs a special virtual machine called SubstrateVM). These native executables start much faster and can use a lot less memory than a traditional JVM, however not every JVM feature is supported, and some are more limited than normal.
 
 For example by default reflection in GraalVM will not work, unless a class/member has been explicitly registered for reflection. This is normally achieved by listing every class, method, field and constructor in a JSON file, and passing this as a parameter into the native image build. This obviously gets quite cumbersome for all but the most trivial projects. Quarkus provides a framework that makes it easy to work around these annotations, and programmatically determine what should be registered.
 
-## How do you unify imperative and reactive programming?
+== How do you unify imperative and reactive programming?
 
 link:/continuum[Learn more].
 
-## What does Container First mean?
+== What does Container First mean?
 
 link:/container-first[Learn more].
 
-## What is your view on standards?
+== What is your view on standards?
 
 link:/standards[Learn more].
 
-## What are you doing to improve developer joy?
+== What are you doing to improve developer joy?
 
 link:/developer-joy[Learn more].