Improve site-builder UX

[mlegner]

• improve the site-builder defaults
• improve the site builder output -> Provide more INFO output and better errors in site-builder #65
• add "dry run" to determine the site creation price
• add confirmation for the transaction

[Tzal3x]

Hey @mlegner can you elaborate more on the following?

1. improve the site-builder defaults
2. add confirmation for the transaction

Is this issue currently developed? If so I can start working on it!

[mlegner]

Oh, that's a very good question. I think I just took those from https://github.com/MystenLabs/walrus/issues/360, so @giac-mysten might know a bit more...

Regarding the defaults, one nice improvement could be not to require the user to specify a config file if they just want to use the default settings and/or look for the config file in some default locations. (Although I'm not sure that was the original intent.)

In any case, nobody is working on this at the moment.

[giac-mysten]

I think "improving the defaults" was about looking for the config files in default locations... Some of this work is already done, but maybe we could have something similar to the walrus binary, where the site-builder looks for the binary in ~/.config (@mlegner did we settle the discussion on where the configs should go?) and then tries ./assets/builder-example.yaml

add confirmation for the transaction

This is a follow up to the --dry-run work. The idea would be for the client to determine the price of creating/updating the site, displaying it to the user, and then asking "publishing/updating will cost XYZ SUI. do you want to proceed with the transaction?". Such that there are no surprises on that front