Skip to content

Commit cd5c61d

Browse files
Update platform.adoc
Changes to aid understanding of the platform: - Changed 2 headings to questions to make engagement with content easier to engage with. - Added a line in the platform description to give a quick summary, introducing the scope of the platform before the details of it. - Added a section 'how does the Quarkus platform help?' with bullet point descriptions to help summarize key value points. Also, for browsing bullets specifically to introduce the concept is helpful upon quick viewing. Update docs/src/main/asciidoc/platform.adoc Update docs/src/main/asciidoc/platform.adoc Update docs/src/main/asciidoc/platform.adoc Update docs/src/main/asciidoc/platform.adoc Co-Authored-By: Alexey Loubyansky <[email protected]>
1 parent 4e66327 commit cd5c61d

File tree

1 file changed

+9
-1
lines changed

1 file changed

+9
-1
lines changed

docs/src/main/asciidoc/platform.adoc

Lines changed: 9 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -11,11 +11,19 @@ include::_attributes.adoc[]
1111

1212
The Quarkus extension ecosystem consists of the Quarkus extensions developed and maintained by the community, including the Quarkus core development team. While the Quarkus ecosystem (sometimes also referred to as the "Quarkus universe") includes all the Quarkus extensions ever developed, there is also a concept of a Quarkus platform.
1313

14-
== Quarkus Platform
14+
== What is the Quarkus Platform?
15+
16+
The Quarkus Platform is a curated set of extensions, tools, and configurations that make it easier to build, test, and deploy Java applications with Quarkus.
1517

1618
The fundamental promise of a Quarkus platform is any combination of the Quarkus extensions the platform consists of can be used in the same application without causing any conflict for each other.
1719
Each organization creating their Quarkus platform may establish their own criteria for the extensions to be accepted into the platform and the means to guarantee the compatibility between the accepted extensions.
1820

21+
== How does the Quarkus Platform help?
22+
When multiple extensions are used in the same project, a Quarkus platform BOM ensures:
23+
* version compatibility between the dependencies;
24+
* simplified dependency management;
25+
* easier upgrades.
26+
1927
=== Quarkus Platform Artifacts
2028

2129
Each Quarkus platform is defined with a few artifacts.

0 commit comments

Comments
 (0)