Experiment to rebuild Diffuse using web applets.
chore: Update index page
+25
-9
+25
-9
src/pages/index.astro
+25
-9
src/pages/index.astro
···
9
9
{ url: "engine/queue/", title: "Queue" },
10
10
];
11
11
12
+
const orchestrators = [
13
+
{ url: "orchestrator/queue/", title: "Queue" },
14
+
{ url: "orchestrator/storage/", title: "Storage" },
15
+
];
16
+
12
17
const themes = [{ url: "themes/pilot/", title: "Pilot" }];
13
18
---
14
19
···
67
72
}
68
73
</ul>
69
74
75
+
<h3>Orchestrators</h3>
76
+
77
+
<p>
78
+
<em
79
+
>These too are applet compositions. However, unlike themes, these are purely logical, and
80
+
optional. Mostly exist in order to construct sensible defaults (eg. applet connections you
81
+
want to reuse across themes).</em
82
+
>
83
+
</p>
84
+
85
+
<ul>
86
+
{
87
+
orchestrators.map((item: any) => (
88
+
<li>
89
+
<a href={item.url}>{item.title}</a>
90
+
</li>
91
+
))
92
+
}
93
+
</ul>
94
+
70
95
<h3>Storages</h3>
71
96
72
97
<p>
···
92
117
>Applets that serve as an intermediate in order to make a particular kind of applet
93
118
configurable. In other words, these allow for an applet to be swapped out with another
94
119
that takes the same actions and data output.</em
95
-
>
96
-
</p>
97
-
98
-
<h3>Orchestrators</h3>
99
-
100
-
<p>
101
-
<em
102
-
>These too are applet compositions. However, unlike themes, these are purely logical, and
103
-
optional. Mostly exist in order to construct sensible defaults.</em
104
120
>
105
121
</p>
106
122