feat(demo): add more content

Author: tomastrajan

projects/elements-demo/src/app/features/docs/faq/faq.component.ts

@@ -45,5 +45,12 @@ const FAQ = [
       'When do we need to use <code>*axLazyElement="module: true"</code> flag?',
     answer:
       'Some web components libraries might be distributed using ES modules, for example if we look at <a href="https://unpkg.com/@material/mwc-button@0.6.0/mwc-button.js?module" target="_blank">@material/mwc-button</a> we will see that it imports additional things like <code>@material/mwc-base</code> using import statement in its implementation. This means it will need to download multiple files compared to a single bundle when using Angular elements. To make this work, library has to generate <code>\t&#60;script type="module"></code> instead of just plain <code>\t&#60;script></code> tag.'
+  },
+  {
+    question: 'Angular elements / web components / custom elements / what?',
+    answer:
+      'In the docs, we often use phrase "Angular elements (or any other web component)" but this may sound a bit vague without previous insight into the topic... <br><br>' +
+      'The web standard is in fact called "Web Components" and it uses <a href="https://developer.mozilla.org/en-US/docs/Web/Web_Components/Using_custom_elements" target="_blank">Custom Elements API</a> to create and use web components which are <strong>new custom, reusable, encapsulated HTML tags</strong> to use in web pages and web apps.<br><br>' +
+      "Angular Elements wraps Angular components using <code>HTMLElement</code> APIs and then uses Custom Elements API, more precisely the <code>customElements.define('some-element', SomeComponentElement)</code> syntax to register it for the use in the web page."
   }
 ];

projects/elements-demo/src/app/features/docs/use-cases/use-cases.component.html

@@ -352,6 +352,13 @@ <h2>Microfrontends style "sub-applications"</h2>
     </g>
   </svg>
 
+  <p>
+    Or we can face situation when we are running different versions of the same
+    widget in various apps which may cause other problems related to breaking
+    changes, incompatible data models which may introduce additional complexity
+    for backends...
+  </p>
+
   <blockquote class="large">
     Wouldn't it be great if we could deploy new version of our widget
     independently from release cycle of consumer applications?