Design Guide – Best Practices for Designing a Terminal Journaling Experience

The first 4 images below (# 2 is also animated on the link) are examples of CLI. The 5th picture is an image of the Heroku newspapers. The last image is the one you usually see in the programs you install from the command line. Basically, a bunch of journaling outputs without too much UX.

I am wondering what is the ideal user experience for a command line interface, especially when it performs an action invoked by the user. For example, brew install x will install something with homebrew (first image) and give you brief status updates and progress bars along the way. then node example.js in the second image, it will go through a few operations while staying on a line (while the homebrew goes through several lines). The others have less structure, display the log output in a stream, formatting it if possible.

The question is, however, what is the ideal user experience. Given the following. If it were to show timestamp actions that have occurred (as do the Heroku logs, but this type of logging may be different from the experience of the CLI introduction tool). S & # 39; he had to print verbose exit somewhere (as in a separate file or on the screen in one way or another), basically all the details of the debugging. Or if it should hide just about everything (# 2) and just give you titles of the current status, such as "Loading x". Or a medium term like (# 1) with status updates that also connect to the stream. I do not know how to think about that.


enter the description of the image here


enter the description of the image here


enter the description of the image here


enter the description of the image here


enter the description of the image here


enter the description of the image here