hello, I was thinking of good way to implement 'skins' for fw/1 application. At one point, I think - what if /views and /layouts to be stored in 'theme' folder and location of 'theme' to be controlled by settings? I know this may sound like rare use case, but as exercise may bring some fun 🙂 Changes in Framework One itself will be required but it's the best path.

Yeah, FW/1 is mature enough at this point that it’s going to be difficult to find a use-case that either hasn’t been considered OR just belongs in the application code instead of modding the framework. It’s hard enough thinking of something @seancorfield or the team hadn’t already considered… the framework is old enough to be plenty mature by now. I like your solution tho… you could package that as a Themes add-on for FW/1, even if it’s really just mostly documentation, not a “plugin” per-se. I believe people will benefit from it!