Iterative Design Guidelines

Question

When your application has a view that is accessible only after sending another form (for example, the registration screen, checking the shopping cart or the master interface), what is the best way to work with subsequent views without having to scroll through all the previous steps?

Let's say we are working on the second or third step of the product build wizard. The first step is to choose a make and model, step 2 - options, the third step - more settings that depend on the choices made in steps 1 and 2. What is the fastest way to get this point of view?

First you create html pages and then convert them to erb? What do you do if it is an existing application and you make changes and do not have the original html to work with?

Answer 1

You can always refresh the page available through POST and resubmit it so that you display the same one again.

You can also create a temporary action that defines some standard values ​​and displays the corresponding erb file.
You can then access your page and refresh it without completing all the previous steps.