[Bug] The CC Vocabulary is not being used

[kewonit]

Description

After looking at fairly new merged pr #122, where instead of using the Vocabulary CDN, the entire global-header component has been hard-coded in.

Expectation

The Vocabulary CDN (for styles & scripts) should be imported in, over having them hard-coded in. As this will help follow the standards & guidance of Open source CC, also maintaining the repo will be ez!
This will fix many other issue that have been raised over time, regarding buggy UI.

Environment

• Device: Laptop
• OS: Ubuntu
• Browser: Chrome
• Version: 99.0.4844.84

Additional context

Importing them directly will make considerable changes, as it would try to overwrite the existing CSS, will have to fix them. The best way to fix this would be to import them in, and then remove the CSS that gets overwritten. Also, I would like to work on this issue.

Resolution

• I would be interested in resolving this bug.

[possumbilities]

@KewKartik The site doesn't currently utilize the Vocabulary CDN since the Vocabulary design system is under a refactor. At the moment it's most stable use is via unpkg and/or use through the Vue.js frontend framework, but even that is in flux.

For the time being, until the Vocabulary codebase is refactored fully there isn't an aim to implement it into the site yet. A similar approach was taken with the search repository as well.

I'm marking this as blocked, since it's something we'd hope to address, but after the Vocabulary codebase itself is in more stable condition for future use.