Capture the essence of a running job via rundeck. This functionality is the beachhead for new users and power users alike. I tried to emphasize the complete sequence from going to a Rundeck instance, to typing a command and seeing output.
The emphasis is on monotony in this user interaction. By stripping away all other UI elements, I believe the resulting flow is much more efficient and natural to a user familiar with the command line.
The one sticking point that I kept revisiting is the duality between Ad-hoc commands and Running pre-baked jobs (or decks as I refer to them in this flow). Tabs are common in may system web interfaces. Splunk, Nagios, Hyperic, etc, all have a tab bar as part of their UI to aid navigation. Splunk goes further and provides a "command line" control that is main interaction point, which is inspiration for the UI design here. For the interaction, I did not explore what the Deck interface would look like and instead focused on the command line execution. I do provide a very small tab on the left hand side that indicates something more. This is in the theme of Get Satifactions Feedback tab. The point is that it is a minimal reference to the other "side" of the product.
What I like about this User Interaction is that it is minimal. All other UI elements are gone except for the filter, browse and command line elements.
This design is by no means complete and is simplistic. I'm missing the security callout (i.e. logged in as: noahcampbell, logout, etc.)
Perhaps more important is the interaction to start another command. Given that the command, filter summary and command output represent a final run, how does one start another command? Do they start typing in the command and the display is reset to filter options, and no browse output. Is there a "new" action in the ui that creates a fresh page?
