fix(welcome): concept cards speak everyday language first
Some checks are pending
Security / Security check (push) Waiting to run
Some checks are pending
Security / Security check (push) Waiting to run
The Hub/Module/Flow cards explained the basics in the very vocabulary they were supposed to introduce (Rust binary, WASM, YAML, hash-chained). Each card now leads with a plain-language explanation; the technical wording moved behind a per-card 'for the technically curious' toggle. DE and EN. Signed-off-by: flemming-it <stefan.a.flemming@googlemail.com>
This commit is contained in:
parent
cc1618f512
commit
3e1ce6e1fd
6 changed files with 163 additions and 28 deletions
|
|
@ -30,11 +30,15 @@
|
|||
"welcomeHeroTitle": "Ch∆In Platform",
|
||||
"welcomeHeroSubtitle": "Deterministic workflow engine for AI-assisted data processing in regulated environments.",
|
||||
"welcomePillarHubTitle": "Hub",
|
||||
"welcomePillarHubBody": "One Rust binary that loads modules and runs flows. SQLite for state. No Docker, no message broker, no background services to babysit.",
|
||||
"welcomePillarHubBody": "The program that runs everything. It works right on your machine, needs no extra software, and keeps everything important in a single file.",
|
||||
"welcomePillarHubTech": "One Rust binary that loads modules and runs flows. SQLite for state. No Docker, no message broker, no background services to babysit.",
|
||||
"welcomePillarModuleTitle": "Module",
|
||||
"welcomePillarModuleBody": "A small WebAssembly component that does one thing. Declares the network endpoints, files, and environment variables it touches; the hub enforces the list.",
|
||||
"welcomePillarModuleBody": "A building block that does exactly one job — reading text out of documents, say. Every module states up front what it wants to touch; the hub allows nothing more.",
|
||||
"welcomePillarModuleTech": "A small, sandboxed WebAssembly component. Declares the network endpoints, files, and environment variables it touches; the hub enforces the list.",
|
||||
"welcomePillarFlowTitle": "Flow",
|
||||
"welcomePillarFlowBody": "A YAML file that chains modules together. Inputs go in, modules run in declared order, outputs come out — every step recorded in a hash-chained audit log.",
|
||||
"welcomePillarFlowBody": "A recipe that connects modules into fixed steps. Inputs go in, steps run in order, the result comes out — and every step is recorded tamper-evidently.",
|
||||
"welcomePillarFlowTech": "A YAML file that chains modules together; every step is recorded in a hash-chained audit log that the Diagnostics page verifies in full.",
|
||||
"welcomePillarTechToggle": "For the technically curious",
|
||||
"welcomeTrustHeader": "TRUST POSTURE",
|
||||
"welcomeTrustSandboxTitle": "Sandbox by default",
|
||||
"welcomeTrustSandboxBody": "Every module ships with an explicit permission list — network endpoints, files, environment variables. The hub enforces it; nothing reaches outside the sandbox without operator approval.",
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue