There are 3 main areas to this Android build file: apply plugin, buildscript, android.
When building an app, Gradle combines a product flavor configuration from each defined flavor dimension, along with a build type configuration, to create the final build variant.
At build time, Gradle generates the BuildConfig class so the app code can inspect information about the current build.
Gradle models its builds as Directed Acyclic Graphs (DAGs) of tasks (units of work). What this means is that a build essentially configures a set of tasks and wires them together — based on their dependencies — to create that DAG. Once the task graph has been created, Gradle determines which tasks need to be run in which order and then proceeds to execute them.
A Gradle plugin packages up reusable pieces of build logic, which can be used across many different projects and builds.
Gradle can create separate APKs that contain only code and resources specific to each density or ABI.
Dependencies refer to the things that supports in building the project. An Android library is structurally the same as an Android app module. It can include everything needed to build an app, including source code, resource files, and an Android manifest. A multi-project build in Gradle consists of one root project, and one or more subprojects.
The rich text element allows you to create and format headings, paragraphs, blockquotes, images, and video all in one place instead of having to add and format them individually. Just double-click and easily create content.
A rich text element can be used with static or dynamic content. For static content, just drop it into any page and begin editing. For dynamic content, add a rich text field to any collection and then connect a rich text element to that field in the settings panel. Voila!
Headings, paragraphs, blockquotes, figures, images, and figure captions can all be styled after a class is added to the rich text element using the "When inside of" nested selector system.