Favor Content over Code / Configuration (ex. metadata)

[thescientist13]

At the initial outset of Greenwood, one of the original ways to provide metadata was through Greenwood's configuration file.

const FAVICON_HREF = '/assets/favicon.ico';
const META_DESCRIPTION = 'A modern and performant static site generator supporting Web Component based development';

export default {
  meta: [
    { name: 'description', content: META_DESCRIPTION },
    { name: 'twitter:site', content: '@PrjEvergreen' },
    { property: 'og:title', content: 'Greenwood' },
    { property: 'og:type', content: 'website' },
    { property: 'og:url', content: 'https://www.greenwoodjs.io' },
    { property: 'og:image', content: 'https://www.greenwoodjs.io/assets/greenwood-logo-300w.png' },
    { property: 'og:description', content: META_DESCRIPTION },
    { rel: 'shortcut icon', href: FAVICON_HREF },
    { rel: 'icon', href: FAVICON_HREF }
  ]
};

As Greenwood stays away from templating languages (other than JS / Web Components) and aims to be more HTML first, static metadata (e.g. content) via configuration eels more like an anti-pattern. It would be just as easy to have that in the HTML. In other words, I think this we should deprecate meta in greenwood.config.js, which would also invalidate #655 and possibly #304.

Also seeing how we can make it easy to get metadata from markdown without needing a templating language - #576 (comment)

Examples / related issues for tracking:

• title configuration should accept a (formatting) function as an option #655
• add support for configuring lang attribute in default template #558
• <meta> Component package #304

[thescientist13]

See #881