Hi, base system model is something like first boot which ensure basic settings after first login to rest-service of target machine. First I describe how it should look from user perspective. User login to target machine and then he see first module from first boot sequency, after saving settings go to next step until last one is complete and then show standard control panel. Implementation proposal: Create new rest-service for first boot. This module store in database last successfully saved module. It also contains list of modules and its order. So frontend ask only what module is next one. If next one is control panel, then first boot is complete passed. Frontend is implemented mostly in control panel. It ask backend for next module in first boot order. If next module is not control panel, then control panel redirect to that module. The most complicated think is how recognize, that module settings is successfully set. My proposal is set to session in control panel, that modul must set status. If user successfully set settings that corresponding module set status to OK and control panel send this information to rest module and look what is next module to pass. pros: * Minimal changes to current code * Easily manageable order and modules in first boot neg: * Each modules must handle request to status * somehow must be solved returning from module to control panel (redirect after success save?), as browser back doesn't work as expected thanks for opinions and suggestions, Josef -- Josef Reidinger YaST team maintainer of perl-Bootloader, YaST2-Repair, webyast modules language and time -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org