Update the dependencies used by the site layout

[duboisp]

I would like to suggest to replace the local dependencies of wet-boew and gcweb by the files hosted on the Canada.ca CDN.

Change the line 45-46 in the basic layout which is:

	<script src="{{ rootPath }}wet-boew/js/wet-boew.min.js"></script>
	<script src="{{ rootPath }}gcweb/js/theme.min.js"></script>

by

	<script src="https://www.canada.ca/etc/designs/canada/wet-boew/js/wet-boew.min.js"></script>
	<script src="https://www.canada.ca/etc/designs/canada/wet-boew/js/theme.min.js"></script>

Idem for the CSS file included in the partial file head.njk at line 14 to be replaced by https://www.canada.ca/etc/designs/canada/wet-boew/css/theme.min.css

From this project we are not going to create our own version of wet-boew or of GCWeb So instead of maintaining a dependencies, Soon wet-boew and gcweb are going to be released 2-3 times per months. I recommend to point to the latest version hosted in Canada.ca. We are not planning to do any breaking changes in wet-boew and gcweb from the web authors point of view.

That don't block us to extend the existing style, like it was already configured neither to submit a PR in wet-boew or GCWeb GitHub repository to fix an accessibility issue.

I will be interested to know why we need to have a custom CSS for this site. Is there missing a feature / a style in GCWeb? Also that information would be useful later for the GC Design System project.

[shawnthompson]

1. Like all others who use WET-BOEW, I fear that an update to that repo might break something we are using. It probably won't but that could still happen, joys of dependencies.

We are not planning to do any breaking changes in wet-boew and gcweb from the web authors point of view.

That doesn't mean it won't happen. And if one of those changes is causes an accessibility issue, not planned, I would hate to have a site on accessibility that doesn't have accessibility first in mind.

2. Presently we are using custom styles for the banner, the contribute section, and the font-awesome icons spacing instead of using mrgn-rght-md in every class, I wanted it to be the same everywhere we use it.

Although I'd love to add the Contribute section in WET-BOEW.

[shawnthompson]

Do we want to move the CSS to GCWeb or WET? I would like to see the base use it. Because I'm still waiting for the Design team to officially approve it. And I'd also like to create different variants.

[duboisp]

It will most likely to be moved in GCWeb. I am currently working on making GCWeb more independent from wet-boew to optimize it like avoiding multiple override.

Because I'm still waiting for the Design team to officially approve it.

What design team you are waiting for?

And I'd also like to create different variants.

Variant of the theme or variant as CMS?

[shawnthompson]

I tagged @pcwsmith in this discussion #64.

I also spoke to @delisma in slack about it.

Maybe you can bring it up during your meeting with them.

I'd really like to create a standards for projects that are open source and a variant for the different platforms, like GIthub, Gitlab, Gitbucket and any other ones I might be forgetting.

I really like it the way it is and to make it stick out that it's an open source project. I'm scared it gets buried in the footer menu or even worse in the main menu.

[duboisp]

Yes I agree that will be nice if guidance was provided on how to make website for open source project. We are still waiting for guidance on how to make website for guidance (like a simple top banner).

[shawnthompson]

Related to: #64

[shawnthompson]

Let's vote on it at the next dev meeting.

[shawnthompson]

Will be moving to CDN and taking the WET dependency out of the package.json.