Added fa-brief and fa-pageability

Signed-off-by: Nwusongqing <wusongqing@huawei.com>

en/application-dev/ability/ability-assistant-guidelines.md

@@ -71,16 +71,17 @@ The ability assistant is pre-installed in the device environment. You can direct
 
   Prints ability related information.
 
-  | Name                  | Description                              |
-  | ---------------------- | -------------------------------------- |
-  | -h/--help              | Help information.                            |
-  | -a/--all               | Ability information in all missions.          |
-  | -s/--stack \<number>   | Ability information in a specified mission stack.    |
-  | -m/--mission \<number> | Ability information in a specified mission.          |
-  | -l/--stack-list        | Mission list in each mission stack.|
-  | -u/--ui                | System UI ability information.               |
-  | -e/--serv              | Service ability information.                 |
-  | -d/--data              | Data ability information.                    |
+  | Name             | Level-2 Parameter            | Description                                                    |
+  | ----------------- | -------------------- | ------------------------------------------------------------ |
+  | -h/--help         | -                    | Prints help information.                                                  |
+  | -a/--all          | -                    | Prints ability information in all missions.                                |
+  | -l/--mission-list | type (All logs are printed if this parameter is left unspecified.)| Prints mission stack information.<br>The following values are available for **type**:<br>NORMAL <br>DEFAULT_STANDARD<br>DEFAULT_SINGLE<br>LAUNCHER |
+  | -e/--extension    | elementName          | Prints extended component information.                                          |
+  | -u/--userId       | UserId               | Prints stack information of a specified user ID. This parameter must be used together with other parameters. Example commands: aa **dump -a -u 100** and **aa dump -d -u 100**.|
+  | -d/--data         |                      | Prints Data ability information.                                          |
+  | -i/--ability      | AbilityRecord ID     | Prints detailed information about a specified ability.                                     |
+  | -c/--client       |                      | Prints detailed ability information. This parameter must be used together with other parameters. Example commands: **aa dump -a -c** and **aa dump -i 21 -c**.|
+  
 
   **Method**
 

en/application-dev/ability/fa-brief.md

+# FA Model Overview
+
+## Overall Architecture
+The development of an OpenHarmony application is essentially the development of one or more abilities. By scheduling abilities and managing their lifecycle, OpenHarmony implements application scheduling. In the FA model, three types of abilities are provided: Page, Service, and Data. The Page ability has the ArkUI and therefore provides the capability of interacting with users. The Service ability does not have a UI. It runs in the background and provides custom services for other abilities to invoke. The Data ability does not have a UI. It also runs in the background and enables other abilities to insert, delete, and query data.
+
+## Application Package Structure
+**The following figure shows the application package structure.**
+![fa-package-info](figures/fa-package-info.png)
+
+## Lifecycle
+
+**The following figure shows the lifecycle of the Page ability.**
+
+![fa-pageAbility-lifecycle](figures/fa-pageAbility-lifecycle.png)
+
+You can override lifecycle functions in **app.js/app.ets** to process application logic.
+
+
+## Process and Thread Model
+An application exclusively uses an independent process, and an ability exclusively uses an independent thread. An application process is created when an ability is started for the first time, and a thread is created for this ability too. After the application is started, other abilities in the application are started, and a thread is created for every of these started abilities. Each ability is bound to an independent JSRuntime instance. Therefore, abilities are isolated from each other.
+
+![fa-threading-nodel](figures/fa-threading-model.png)

en/application-dev/ability/fa-pageability.md

+# Page Ability Development
+
+## Overview
+### Concepts
+The Page ability has the ArkUI and therefore provides the capability of interacting with users. When you create an ability in the integrated development environment (IDE), the IDE automatically creates template code. The capabilities related to the Page ability are exposed through the singleton **featureAbility**, and the lifecycle callbacks are exposed through the callback functions in **app.js/app.ets**.
+
+### Page Ability Lifecycle
+
+The ability lifecycle is a general term for all states of an ability (either a Page or a Service ability), such as **INACTIVE**, **ACTIVE**, and **BACKGROUND**.
+
+The following figure shows the lifecycle state transition of the Page ability.
+
+![PageAbility-Lifecycle](figures/page-ability-lifecycle.png)
+
+
+Description of ability lifecycle states:
+
+  - **UNINITIALIZED**: The ability is not initialized. This is a temporary state. An ability changes directly to the **INITIAL** state upon its creation.
+
+  - **INITIAL**: This state refers to the initial or stopped state. The ability in this state is not running. The ability enters the **INACTIVE** state after it is started.
+
+  - **INACTIVE**: The ability is visible but does not gain focus.
+
+  - **ACTIVE**: The ability runs in the foreground and gains focus.
+
+  - **BACKGROUND**: The ability returns to the background. After being re-activated, the ability enters the **ACTIVE** state. After being destroyed, the ability enters the **INITIAL** state.
+
+**The following figure shows the lifecycle of the Page ability.**
+
+![fa-pageAbility-lifecycle](figures/fa-pageAbility-lifecycle.png)
+
+You can override the lifecycle callback functions provided by the Page ability in **app.js/app.ets**.
+
+## Development Guidelines
+### Available APIs
+
+**Table 1** APIs provided by featureAbility
+
+| API                                             | Description           |
+| --------------------------------------------------- | --------------- |
+| void startAbility(parameter: StartAbilityParameter) | Starts an ability.    |
+| Context getContext():                               | Obtains the application context.|
+| void terminateSelf()                                | Terminates the ability.    |
+| bool hasWindowFocus()                               | Checks whether the ability gains focus.   |
+
+
+### Starting a Local Page Ability
+
+* Modules to Import
+
+```
+import featureAbility from '@ohos.ability.featureAbility'
+```
+* Example
+
+```javascript
+import featureAbility from '@ohos.ability.featureAbility'
+featureAbility.startAbility({
+  want:
+  {
+    action: "",
+    entities: [""],
+    type: "",
+    options: {
+      // Grant the permission to read the URI.
+      authReadUriPermission: true,
+      // Grant the permission to write the URI.
+      authWriteUriPermission: true,
+      // Forward the intent result to the origin ability.
+      abilityForwardResult: true,
+      // Mark the ability start-up triggered by continuation.
+      abilityContinuation: true,
+      // Specify that a component does not belong to ohos.
+      notOhosComponent: true,
+      // Specify whether an ability is started.
+      abilityFormEnabled: true,
+      // Grant the permission to persist the URI.
+      authPersistableUriPermission: true,
+      // Grant the permission to persist the URI.
+      authPrefixUriPermission: true,
+      // Support distributed scheduling and start-up across multiple devices.
+      abilitySliceMultiDevice: true,
+      // An ability using the Service template is started regardless of whether the
+      // host application has been started.
+      startForegroundAbility: true,
+      // Install the specified ability if it is not installed.
+      installOnDemand: true,
+      // Return the result to the origin ability slice.
+      abilitySliceForwardResult: true,
+      // Install the specified ability with the background mode if it is not installed.
+      installWithBackgroundMode: true
+    },
+    deviceId: "",
+    bundleName: "com.example.startability",
+    abilityName: "com.example.startability.MainAbility",
+    uri: ""
+  },
+},
+);
+```
+You can also include **parameters** in the **want** parameter and set its value in the key-value format.
+* Example
+```javascript
+import featureAbility from '@ohos.ability.featureAbility'
+featureAbility.startAbility({
+    want:
+    {
+        bundleName: "com.example.startability",
+        uri: "",
+        parameters: {
+            abilityName: "com.example.startability.MainAbility"
+        }
+    },
+},
+);
+```
+### Starting a Remote Page Ability
+
+* Modules to Import
+
+```
+import featureAbility from '@ohos.ability.featureAbility'
+```
+
+* Example
+
+```javascript
+var promise = await featureAbility.startAbility({
+    want:
+    {
+        deviceId: this.deviceId,
+        bundleName: "com.example.test",
+        abilityName: "com.example.test.MainAbility",
+    },
+}
+);
+```
+### Lifecycle APIs
+**Table 2** Lifecycle callback functions
+
+| API      | Description                                                        |
+| ------------ | ------------------------------------------------------------ |
+| onShow()     | Invoked when the ability is switched from the background to the foreground. In this case, the ability is visible to users.|
+| onHide()     | Invoked when the ability is switched from the foreground to the background. In this case, the ability is invisible.|
+| onDestroy()  | Invoked when the ability is destroyed. In this callback, you can make preparations for app exit, such as recycling resources and clearing the cache.|
+| onCreate()   | Invoked when the ability is created for the first time. You can initialize the application in this callback.|
+| onInactive() | Invoked when the ability loses focus. An ability loses focus before entering the background state.|
+| onActive()   | Invoked when the ability is switched to the foreground and gains focus.     |
+
+* Example
+You need to override the lifecycle callback functions in **app.js/app.ets**. The IDE template generates **onCreate()** and **onDestroy()** by default. You need to override the other functions.
+```javascript
+export default {
+  onCreate() {
+    console.info('Application onCreate')
+  },
+  onDestroy() {
+    console.info('Application onDestroy')
+  },
+  onShow(){
+    console.info('Application onShow')
+  },
+  onHide(){
+    console.info('Application onHide')
+  },
+  onInactive(){
+    console.info('Application onInactive')
+  },
+  onActive(){
+    console.info('Application onActive')
+  },
+}
+```
+### Development Example
+The following sample is provided to help you better understand how to develop a Page ability:
+
+- [DMS](https://gitee.com/openharmony/app_samples/tree/master/ability/DMS)
+
+This sample describes how to start a local ability and remote ability.