No Deployments Empty State Block for React

No. The page never runs the command; it prints it for you to run in your own project. The sample run is typed text at fixed times, the deployment it lists is a row in the page's state, and the host in its last line is made up. A reload clears it, and Start over clears it without one. To wire it for real, list the deployments your API returns instead of the typed row.

It is built from the environment you pick and the switch: moorage deploy --env staging, with --skip-tests added when the switch is on. The terminal's command is a labelled region that scrolls sideways on a narrow screen, so a long command never makes the page scroll. The Copy command button copies exactly what is shown, and a polite line says it worked or that the clipboard refused it.

Terminals are dark by nature, so this one carries its own dark scope while everything around it follows the theme (a code comment says so). Its text is real text, its output is a log region you can focus and scroll with the keyboard, and its muted lines pass contrast in the dark scope.

It prints six typed lines, each fading in a moment after the last, with the environment and the switch you had at that moment, and lists Deployment 1 under the terminal. The tether in the drawing turns solid and the balloon fills. The entrance is a CSS transition and shows all at once under reduced motion. Start over, which stays quiet until there is a deployment, puts the dashed tether back and focus on Copy command.

No. The terminal's output area has one height, the list is one row high whether it is dashed or holds a deployment, and the status line has a place of its own. The page is centred, so nothing may grow; this is why.

The balloon sits above the heading at 140 px tall, the form stacks, the terminal scrolls sideways inside itself, and the Copy command button is pinned to the foot of the screen with the status line above it.