Re: [w3c/manifest] Relationship between nestedly scoped web app manifests? (#539)

Just to jump into the discussion:
In ERP systems, there is usually an empty shell with a basic layout, general functionality such as logging in, out, etc., and a set of so-called `modules`. These modules are packages of functionality that are usually developed by different teams and then deployed into the shell. They have their own manifests while they know an upper application exists that also has a manifest.
In this setting, some upper manifest elements such as the `icon` should be propagated to the shell and any module. 
Elements such as `title` may be propagated and concatenated with that of the modules (if they exist). E.g., <App Name>: <Module Name> in the title bar.
Some other elements such as `theme` and `color`, should be taken from the parent as default (fallback) but overridden by the modules (if they have matching elements with valid values.)
This is something I have been doing in a few applications that I have been designing or otherwise involved.
Thanks


-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3c/manifest/issues/539#issuecomment-1245673113
You are receiving this because you are subscribed to this thread.

Message ID: <w3c/manifest/issues/539/1245673113@github.com>