Publish all redesign blocks, header, footer, etc from USA repo to Canadian repo

[ZoeBeykirch]

Agile requirement: The user experience on the Volvo Trucks Canadian (English and French language) should be seamless in matching the newly redesigned on-brand experience as the USA site.

Acceptance criteria:

• The French and English Canadian site header should match the USA new header
• The French and English Canadian site sub-header should match the USA new sub-header
• The French and English Canadian site footer should match the USA new footer
• The French and English Canadian site component blocks should match the USA new redesigned blocks

[shirin27]

Requirement:

• [x] Ensure that the language can be configured
• [x] Ensure that the right path can be configured for the navigation
• [x] Make search configurable -> check if it is needed, considering we are using global search

NOTE: To be discussed by @cogniSyb and Adobe for a final solution design, and then refined with the team.

[cogniSyb]

Development is being done in https://github.com/hlxsites/vg-volvotrucks-us/issues/530.

Right now I’m testing some pages.

• [ ] Several pages are copied, but not set to preview yet – I’ve asked Varun to take care of this. Once this is resolved, I can continue with some regression testing of my changes and we can discuss the next point

• [ ] Also, we need to have a short talk about redirects. Currently there’s a lot of pages that are set up differently, not in their own folder. For example: https://www.volvotrucks.ca/en-ca/trucks/vnr-electric vs. https://www.volvotrucks.us/trucks/vnr-electric/. This can have impact on the functionality of some blocks on pages. It’s best to maintain the same structure and end up with files like vnr-electric/index.docx instead of vnr-electric.docx

• [ ] I notice that the header and footer content isn’t correct on the French part.

• For example: 'Trucks' in the header links to /trucks/ whereas it should link to /fr-ca/trucks/

• For example: 'Volvo VNL […] Long haul efficiency – premium comfort.' whereas it is on live website 'Série Volvo VNL […] Efficacité longue distance - confort optimal.'

• [x] The header isn’t the last version, it doesn’t contain a link the the All-New VNL. Also the homepage needs to be updated, and probably we have other outdated pages

• [ ] Some translations might need to be done for /fr-ca/placeholder.xlsx. I’ve updated the file /en-ca/placeholder.xlsx with the content of the US version. I wanted to do that after https://github.com/hlxsites/vg-volvotrucks-us/issues/529 is done, but we haven’t decided to put that in the sprint yet.

• [ ] @ZoeBeykirch since the new header doesn’t contain a link to the 'Select Market' page, is it a blocker for Marketing if users need to scroll to the footer? In any case, the content of 'Country / Region' can be edited

• [x] The All-New VNL page contains broken links to the modals, which made me find a bug. The URLs in question need to be updated

[BeckyMedlin]

@cogniSyb For the French header/footer, I think this ticket is related: https://github.com/hlxsites/vg-macktrucks-ca/issues/22 (it's for all markets, not just Mack).

[cogniSyb]

Good catch @BeckyMedlin. As the content is hardcoded, I’d like to receive a translation of the 404 content as well. It’ll be an easy fix :)

[cogniSyb]

Question related to Pardot

• [x] Do we need to make adjustments/create a copy of the 'subscribe to newsletter' form on the VT homepage, when we roll it out on https://www.volvotrucks.ca? We need to be aware that we have both https://www.volvotrucks.ca/en-ca/ and https://www.volvotrucks.ca/fr-ca/ to deal with

[ryanropero]

@cogniSyb we can do this two ways 1) We add an additional field for Form Name and you can populates it with "Newsletter US" " Newsletter CA-EN" or " Newsletter CA-FR" or something like that. 2) We have 3 separate forms and I can identify what site it is from.

[cogniSyb]

@ryanropero thanks, I’ll add a hidden form field and will make changes for some text that is currently hardcoded.

Seems like a better idea to have separate forms per country, but if you can filter it in this way, then it’s less work for development :)

[Joesturbo]

@BeckyMedlin - can we add to SRB?

@cogniSyb - would it make better sense to create a separate repo for Canada French vs. trying to fix all of the issues here? Thinking out loud to be more efficient.

[Kannan-CM]

Hi @cogniSyb ,

The content task is completed

[BeckyMedlin]

@cogniSyb @shirin27 @mollyaljenkins @Kannan-CM completed the content tasks requested for this ticket. Syb can proceed with the dev work.

[girishdigrajkar]

Observed content issues for en-ca : #53 & for fr-ca #54 Except for these we can proceed with this ticket.