From 20cc844733c266dd0c650f3881b27a64bf5eac90 Mon Sep 17 00:00:00 2001 From: Adam Samalik Date: Jul 04 2019 18:35:28 +0000 Subject: add examples to the homepage --- diff --git a/modules/ROOT/pages/index.adoc b/modules/ROOT/pages/index.adoc index 9779df4..c331ed3 100644 --- a/modules/ROOT/pages/index.adoc +++ b/modules/ROOT/pages/index.adoc @@ -2,16 +2,25 @@ Modularity enables you to choose a particular stream (major version) of content that has been natively built and tested for your system, and to receive the right updates for it. -That means you no longer need to enable "rawhide" repositories to get a new version of a database, or to be prevented from performing a system upgrade to a new Fedora release just because a language runtime got a major upgrade. - image::fedora-without-modularity.png[,100%,] image::fedora-with-modularity.png[,100%,] -Because the same module stream is often available to multiple Fedora releases, you can choose to consume a particular stream regardless of what Fedora release version you're running. Thanks to that, your applications and your system can be upgraded to their next major version independently from each other. +That means you're no longer limited to a single version of each package for a given Fedora release. And because many streams are now available in multiple Fedora releases, you can install a specific version of software regardless of what Fedora release you're running. + +== Examples + +**Scenario 1**: Some users install packages coming from a different Fedora release in order to consume a specific version of a database that is compatible with their application. But thanks to Modularity they might not need to do that anymore, because multiple versions of the database can available in each Fedora release. All they need to do is to consume the specific stream of that database right from the Fedora repositories for their system. + +**Scenaro 2:** There were cases when users couldn't upgrade their system to a new Fedora release because their application wouldn't function with the new version of a language runtime coming with the upgrade. Modularity can fix this problem by providing the same language versions in both Fedora releases. With that, the user can consume a specific stream of the language and keep it even when they upgrade their system. And when the application is ready for the new language version, it can be upgraded later, independently from the OS, by switching to a different stream. == Compatibility -Modularity is built to be 100% compatible with workflows that do not expect Modularity to be present. +Modularity is built to be 100% compatible with existing expectations and workflows. The installation and update experience continues to work the same way — even when there are multiple versions of packages — thanks to default streams. + +For example, the following two commands work the same way on systems with and without Modularity: + + $ dnf install httpd + $ dnf update -Default streams are provided so you only need to make choices when you want to. Your usual installation commands continue to work, automatically consuming content from the default streams. \ No newline at end of file +On systems with multiple httpd streams available, the default stream is automatically enabled and consumed. xref:using-modules.adoc[Learn more about using modules]. \ No newline at end of file