Frequently Asked Questions

Why are there components in the catalog which do obviously not comply with the 6M specification?

Before we introduced a formal specification for 6M, there were already components in use. We decided that these components may remain as they are, as they are already integrated, and a rewrite doesn’t make sense. Some other components are built by older versions of the standard, so they were compliant at the time of their first release.

While the 6M standard evolves, and eventually produces breaking changes, older components are still welcome in the ecosystem, and we will try to support them as much as possible.

We have a microfrontend-like component, but it doesn’t comply with 6M standards. Can we use it as a 6M component anyway?

We are happy about every application that is implemented as a microfrontend. If it is useful, platforming teams will certainly find a way to integrate it.

At the same time, we would encourage you to do the small extra effort to make your microfrontend 6M-compliant. Because if every microfrontend has to be integrated differently, it will cause a lot of overhead and other problems. With an ecosystem of standard-compliant components, on the other hand, our platform teams can build user experiences very quickly and roll them out to our customers.

Isn’t a webcomponent bad for SEO?

No, mostly for two reasons: Modern search engines are able to render JavaScript, and they see the web component just like a normal user. You can prefill the web component with static content as a placeholder, a so-called “skeleton”.