Skip to content

Commit c794cbb

Browse files
feat: reorder misc and integrate provisioning options (#367)
Signed-off-by: David Dal Busco <david.dalbusco@outlook.com>
1 parent 2c744ae commit c794cbb

File tree

7 files changed

+25
-45
lines changed

7 files changed

+25
-45
lines changed

docs/create-a-satellite.mdx

Lines changed: 0 additions & 25 deletions
Original file line numberDiff line numberDiff line change
@@ -24,30 +24,5 @@ Before integrating Juno into your project, you need to create a [satellite].
2424
6. Once the process is complete, click **Continue** to access the overview page.
2525
7. You are all set! Start Building now 🚀
2626

27-
---
28-
29-
## Advanced Options
30-
31-
In the creation wizard, there are advanced options available for more experienced developers or those with specific requirements.
32-
33-
### Selecting a Subnet
34-
35-
If you wish to have more control over where your satellite is deployed, you can select the [subnet] for deployment during the creation process.
36-
37-
Below is a list of available subnets with relevant metadata to help you choose the most appropriate one:
38-
39-
:::note
40-
41-
Satellites operating on larger subnets with more nodes will incur higher cycle costs compared to those running on the standard 13-node subnets. However, this increased cost comes with the benefit of enhanced security due to the greater size of the subnet.
42-
43-
For standard applications, we generally recommend using the standard subnets and staying on the same subnets as Juno.
44-
45-
:::
46-
47-
import Subnets from "./components/subnets.md";
48-
49-
<Subnets />
50-
5127
[satellite]: terminology.md#satellite
5228
[Internet Identity]: terminology.md#internet-identity
53-
[subnet]: terminology.md#subnet

docs/miscellaneous/best-practices.md

Lines changed: 0 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,3 @@
1-
---
2-
sidebar_position: 7
3-
---
4-
51
# Best Practices
62

73
This page provides recommendations to improve your application when developing and deploying with Juno.

docs/miscellaneous/controllers.md

Lines changed: 0 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,3 @@
1-
---
2-
sidebar_position: 5
3-
---
4-
51
# Controllers
62

73
Controllers play a crucial role in granting permissions to mission controls and satellites within Juno.

docs/miscellaneous/memory.md

Lines changed: 0 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,3 @@
1-
---
2-
sidebar_position: 4
3-
---
4-
51
# Memory
62

73
A [satellite] can store data using two types of memory: `heap` and `stable`. While both types are forms of random-access memory that only exist as long as the smart contract lives, they can be compared to a familiar analogy. Think of `heap` as similar to the RAM in a computer, and `stable` as more akin to ROM.
Lines changed: 25 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,25 @@
1+
# Provisioning Options
2+
3+
The creation wizard for Satellites and Orbiters includes advanced provisioning options for developers who need more control.
4+
5+
---
6+
7+
### Selecting a Subnet
8+
9+
If you want more control over where your module is provisioned, you can select a [subnet] during the creation process.
10+
11+
Below is a list of available subnets with relevant metadata to help you choose the most appropriate one:
12+
13+
:::note
14+
15+
Satellites and Orbiters running on larger subnets with more nodes will incur higher cycle costs compared to those on the standard 13-node subnets. However, this increased cost comes with the benefit of enhanced security due to the greater size of the subnet.
16+
17+
For most applications, we recommend using the default subnets and staying on the same subnet as Juno.
18+
19+
:::
20+
21+
import Subnets from "../components/subnets.md";
22+
23+
<Subnets />
24+
25+
[subnet]: terminology.md#subnet

docs/miscellaneous/wallet.md

Lines changed: 0 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,3 @@
1-
---
2-
sidebar_position: 8
3-
---
4-
51
# Wallet
62

73
This section provides guidance on managing your assets and cycles with your [wallet](../terminology.md#wallet), which are essential for maintaining and providing enough resources for your modules in the Juno ecosystem.

docs/miscellaneous/workarounds.md

Lines changed: 0 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,3 @@
1-
---
2-
sidebar_position: 9
3-
---
4-
51
# Workarounds
62

73
This page is dedicated to helping you make the most of Juno features, even when some functionalities are not yet fully supported out of the box. Below, you'll find practical workarounds and guidance for processes which in the future will be resolved by features planned in the [roadmap](../white-paper/roadmap.mdx).

0 commit comments

Comments
 (0)