Hi, the requirements for WebYaST contain a couple of vendor-configurable parts. Some are on the frontend (branding), some on the backend (setup workflow, services, ...). The current approach is to implement vendor configurations spread among many backend modules. I wonder if this is the right approach and if it wouldn't be better to have a single, shared implementation (class ? service ?) to cover this all. A single implementation would ensure consistency in file formats and locations as well as a single documentation. This is mostly for Josef and Jiri to agree upon ;-) Klaus --- SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org