rebrand docs content for beOS Pro

This commit is contained in:
2026-03-09 10:19:35 +01:00
parent 150f4a8ef4
commit d4e933688d
616 changed files with 6294 additions and 6294 deletions

View File

@@ -6,15 +6,15 @@ outline: [2, 3]
## Install and Launch Studio
1. Install [Studio](https://market.olares.com/app/studio) from the Olares Market.
2. Find the Studio icon in the launcher panel on the Olares Desktop.
1. Install [Studio](https://market.beos.local/app/studio) from the beOS Pro Market.
2. Find the Studio icon in the launcher panel on the beOS Pro Desktop.
3. Click on the icon to launch the application.
![main screen](/images/developer/develop/tutorial/create/home.jpg)
## Create Your App
Click the **Create a new application** to create a blank Olares application from a template.
Click the **Create a new application** to create a blank beOS Pro application from a template.
- In the **App Name** field, enter your application name.
- Set the **APP type** to **app**.
@@ -25,7 +25,7 @@ Click the **Create a new application** to create a blank Olares application from
## Setup App Config
After creating the application, you can see the Olares Application Chart files generated by Studio under the **Files** Tab. You can add, delete, or rename various configuration files as needed.
After creating the application, you can see the beOS Pro Application Chart files generated by Studio under the **Files** Tab. You can add, delete, or rename various configuration files as needed.
![upload icon](/images/developer/develop/tutorial/create/add-file.jpg)
@@ -33,9 +33,9 @@ After creating the application, you can see the Olares Application Chart files g
The `Chart.yaml` file is a required file in the Helm Chart specification. It contains the application's `Name` and `Chart Version`. You can [learn more here](https://helm.sh/docs/topics/charts/). For now, we're not going to change the default `Chart.yaml` yet.
### OlaresManifest.yaml
### beOS ProManifest.yaml
In the `OlaresManifest.yaml `file, you can change many configurations. This includes but is not limited to:
In the `beOS ProManifest.yaml `file, you can change many configurations. This includes but is not limited to:
- Changing the app's title, icon, and other details
- Adding system `middleware`
@@ -87,7 +87,7 @@ These parameters should not be hardcoded, they must reference the variables pass
#### Adding [Access Permissions to the File System](../../package/manifest.md#permission)
To read and save files in the Olares system, we need to configure Access Permissions for certain file directories. These directories can be specified in the `Permissions` section of the `OlaresManifest.yaml` file:
To read and save files in the beOS Pro system, we need to configure Access Permissions for certain file directories. These directories can be specified in the `Permissions` section of the `beOS ProManifest.yaml` file:
- `appData`: This applies for independent cloud storage space for the app.
- `appCache`: This applies for local disk data cache space, usually on an SSD disk, for the app.