Commit

a88e545

Re-read. I'd missed Traceability. From now on every commit gets Requested-in: trailers for the dev-null commits behind it, and the PR body links them. The two doc commits already pushed lack them; the PR description will cover those rather than force-pushing.
I would like to revamp this configuration so it is more modular. Can you prototype a few UI examples so I can choose from it? Also, where can I configure the provisioning script?
I think we don't need the switch inside the list. Just go to the details and switch it on or off because currently it is not clear when you configure that you can go inside and adjust it. Furthermore, I think it is fine to have SMB on non-Tailnet setup because each compose…
On mobile, the stepper looks off because the step number circles wrap into the second line. For the your own app, I'm not sure if this is needed because now we can just create components on our own and we already have the provisioning script and stuff like that. Personally, I…
Yeah. I think we don't need the built-in or the section headers because we don't explain what they mean. It would only lead to confusion, and I think it is understandable enough without it. Let's do it!
On it: B becomes the real What runs step, without the headers or the Built-in label, and the startup script goes into compose.yaml for real. I'll open it as a PR on top of #41.

commit a88e545