Re-think going back and forth between web UI and CLI

[lukpueh]

It was noted that the current flow requires a lot of switching between the web interface and the user's terminal.

1. (web) start
2. (cli) install in-toto
3. (web) pick steps and inspections for vcs, building, qa and packaging
4. (web) tweak supply chain
5. (web) create functionaries
6. (cli) create functionary keys
7. (web) upload functionary keys
8. (web) authorize functionaries
9. (web) read about chaining and copy in-toto-mock snippet
10. (cli) run in-toto-mock snippet
11. (web) upload mock link files
12. (web) download layout
13. (cli) generate project owner key
14. (cli) sign layout
15. (web) read where to go from there

It was suggested that we should reduce the amount of times the user has to go back and forth, by re-ordering tasks (e.g. create all keys at once) and/or re-locating tasks (e.g. move the layout creation to the client side)

[procrypt]

Sounds good to me, I can pick it up. As I have to go through the code it'll be a good issue to start with. WDYT @lukpueh

[lukpueh]

Sure! How would you go about?

[procrypt]

I was thinking to refactor the code in a such a way that all the cmd line tasks are done first by the user and then we move to the web console.

[lukpueh]

I fear it is not a pure coding but first of all a UX task. There is a reason for the current workflow. Some of the CLI activities require information from the web UI and vice versa. So before we start refactoring the code, we should probably jot down the improved workflow.