---
New software version notes:

This commit updates to Nuxt 2.9.2. The new version has some implications when coming from 2.8.X version using Typescript:
https://typescript.nuxtjs.org/migration.html

Due to this bug:
markmarkoh/datamaps#500
A custom version of datamaps is used for rendering the Advocate Map:
https://github.com/delapuente/datamaps/tree/fix-types
---

The new theme makes extensive use of dark and electric colors with a vibrant header, combining different styles of sections with ad-hoc widgets to showcase the capabilities of the design. Affected pages are `/education` and `/advocates`.

The new design integrates with qiskit.org by faking the top menu and adding an internal community sub-menu. It also adds a footer with Qiskit elements, community sub-sections and social media.

This commit adds a new component structure aimed at creating a collection of highly composable units. These units use BEM for internal styling. It is recommended not to style the components outside their physical boundaries to give the page freedom to integrates. However, the CSS framework (which is now SCSS) provide a collection of mixin for standarizing the layout.

The point of entry for the community is redirecting to the education micro-site on purpose.

This commit intentionally breaks the separation between design and presentation. A better approach is needed to allow content documents to be able of providing several HTML sections instead of only one. A summary of the problem can be found at:
https://michaelnthiessen.com/advanced-vue-controlling-parent-slots

The most semantic solution, [portals](https://github.com/LinusBorg/portal-vue), don't work in server-side rendering mode and so, the portals are not populated with content in a static-site configuration. We are exploring embedding multiple front-matter documents at:
https://github.com/delapuente/frontmatter-markdown-loader/tree/multiple

The other solutions also rely on client reactivity which is not the desired behaviour.

The new design also intentionally avoids the use of the `<nuxt-link>` component. Due to unknown reasons, DOM differentiation does not work correctly and the navigation is ultimately broken.

Follow-ups for solving the navigation issues, improve reactivity in secondary content and recover the separation between design and content are filled in the project repository.

---
New software version notes:

This commit updates to Nuxt 2.9.2. The new version has some implications when coming from 2.8.X version using Typescript:
https://typescript.nuxtjs.org/migration.html

Due to this bug:
markmarkoh/datamaps#500
A custom version of datamaps is used for rendering the Advocate Map:
https://github.com/delapuente/datamaps/tree/fix-types
---

The new theme makes extensive use of dark and electric colors with a vibrant header, combining different styles of sections with ad-hoc widgets to showcase the capabilities of the design. Affected pages are `/education` and `/advocates`.

The new design integrates with qiskit.org by faking the top menu and adding an internal community sub-menu. It also adds a footer with Qiskit elements, community sub-sections and social media.

This commit adds a new component structure aimed at creating a collection of highly composable units. These units use BEM for internal styling. It is recommended not to style the components outside their physical boundaries to give the page freedom to integrates. However, the CSS framework (which is now SCSS) provide a collection of mixin for standarizing the layout.

The point of entry for the community is redirecting to the education micro-site on purpose.

This commit intentionally breaks the separation between design and presentation. A better approach is needed to allow content documents to be able of providing several HTML sections instead of only one. A summary of the problem can be found at:
https://michaelnthiessen.com/advanced-vue-controlling-parent-slots

The most semantic solution, [portals](https://github.com/LinusBorg/portal-vue), don't work in server-side rendering mode and so, the portals are not populated with content in a static-site configuration. We are exploring embedding multiple front-matter documents at:
https://github.com/delapuente/frontmatter-markdown-loader/tree/multiple

The other solutions also rely on client reactivity which is not the desired behaviour.

The new design also intentionally avoids the use of the `<nuxt-link>` component. Due to unknown reasons, DOM differentiation does not work correctly and the navigation is ultimately broken.

Follow-ups for solving the navigation issues, improve reactivity in secondary content and recover the separation between design and content are filled in the project repository.