- From: Ben Francis <notifications@github.com>
- Date: Fri, 10 Apr 2015 12:01:33 -0700
- To: w3c/manifest <manifest@noreply.github.com>
- Message-ID: <w3c/manifest/issues/350/91652497@github.com>
> Some of my issue with this is that the meta tags describe things related to the page and the manifest describes things relate to an installable experience and it is a subtle difference. I think this is the key point. If a web site is a collection of web pages then a web app is an installable web site, not an installable web page. Until now we've not really had a way to provide metadata about a web site as a whole, only about individual pages, the manifest provides this. I'm not sure a web page is the right place to store metadata about a web site. This would require adding metadata like below to every page of a web site: ``` <meta name="application-lang" content="en"> <meta name="application-name" content="My App"> <meta name="application-short-name" content="My"> <meta name="application-scope" content="/"> <meta name="application-icon" content="/icon.png"> <meta name="application-display" content="standalone"> <meta name="application-orientation" content="portrait"> <meta name="appllication-start-url" content"="/index.html"> <meta name="application-theme-color" content="blue"> ``` You could do it like that, in the same way that you could inline your CSS on every page. It just seems more efficient to put it in a separate file and link to it with a link relation, like we do with other resources that are shared between multiple pages of a web site, like stylesheets. --- Reply to this email directly or view it on GitHub: https://github.com/w3c/manifest/issues/350#issuecomment-91652497
Received on Friday, 10 April 2015 19:02:00 UTC