feat(merative-history): add static build artifacts

[proeung]

Issue

Fixes https://jira.wh-sdlc.watson-health.ibm.com/browse/MERATIVE-726

Description

Changed

• This PR adds the static build artifacts (html/css/js) of the Merative's History page (https://www.ibm.com/resources/watson-health/merative-history/) that's currently hosted on ibm.com.
• New directory /resources/history/
• We need a way to host these files because IBM will most likely sunset this URL on June 30, 2023.

Note

• We need to figure out a way to set index.html as the home of /resources/history/

Design Specs

• Figma Link - N/A

Test URLs

• Before (Changes from main): https://main--merative2--hlxsites.hlx.live/
• After (Changes from this PR): https://feat-add-merative-history--merative2--proeung.hlx.page/resources/history/index.html

Testing Instruction

• Open the IBM-hosted version of Merative's history - https://www.ibm.com/resources/watson-health/merative-history/
• Compare it with the version in this repo - https://feat-add-merative-history--merative2--proeung.hlx.page/resources/history/index.html
• Ensure that the design and interaction is the same.

[aem-code-sync[bot]]

Hello, I'm Franklin Bot and I will run some test suites that validate the page speed. In case there are problems, just click the checkbox below to rerun the respective action.

• [ ] Re-run PSI Checks

[aem-code-sync[bot]]

Page	Scores	Audits	Google
/resources/history/index.html

[aem-code-sync[bot]]

Page	Scores	Audits	Google
/resources/history/index.html

[proeung]

@keith-kaplan @nimithshetty17 I decided to host these static build artifacts in the /resources/history of this repo and it seems to work. Can you take a look at the DOM elements of the index.html and let me know if there are other tags that are missing? I added the Adobe Tag Manager, but I'm sure there is other metadata that's needed.

[proeung]

Note: Also, LHS might be low because these images are in .png. I can convert them into .webp, if we feel good about what's in this PR.

[helms-charity]

I see a problem with putting this under /resources, because that is going to AEMaaCS I believe. You should put it in a different folder.

[aem-code-sync[bot]]

Page	Scores	Audits	Google
/resources/history/index.html

[aem-code-sync[bot]]

Page	Scores	Audits	Google
/resources/history/index.html

[aem-code-sync[bot]]

Page	Scores	Audits	Google
/resources/history/index.html

[proeung]

@keith-kaplan The One Trust script has been added (see - https://github.com/hlxsites/merative2/pull/251/commits/6f7ca7f1f1aa3f1770f421a623279256c9507984).

I see a problem with putting this under /resources, because that is going to AEMaaCS I believe. You should put it in a different folder.

@helms-charity That shouldn't be an issue as we're going to remove the /resource from AEMaaCS.

@nimithshetty17 Can you remove any references of /resources or /resources/history on our AEM's environments? Next step is to change the CDN routing of /resources back to Franklin.

[aem-code-sync[bot]]

Page	Scores	Audits	Google
/resources/history/index.html

[proeung]

Marking this PR as "On-Hold" until we know which copy to use for the rebranding SPM to Cúram (see - https://merative.monday.com/boards/3096780490/views/92911261).

[aem-code-sync[bot]]

Page	Scores	Audits	Google
/resources/history/index.html

[aem-code-sync[bot]]

Page	Scores	Audits	Google
/resources/history/index.html

[proeung]

Added copy changes based on the changes outlined in this Monday.com card (https://merative.monday.com/boards/3096780490/views/92911261/pulses/4537485904/posts/2239610770).

@venky-moonraft @keith-kaplan Can you take a look?

https://feat-add-merative-history--merative2--proeung.hlx.page/resources/history/index.html

[keith-kaplan]

@proeung may we please move the Tag manager script below the Onetrust script? The Onetrust script needs to load first so if visitors choose to not accept cookies, some of the tag manager scripts won't load.

[aem-code-sync[bot]]

Page	Scores	Audits	Google
/resources/history/index.html

[aem-code-sync[bot]]

Page	Scores	Audits	Google
/resources/history/index.html

[proeung]

@proeung may we please move the Tag Manager script below the Onetrust script? The Onetrust script needs to load first so if visitors choose to not accept cookies, some of the tag manager scripts won't load.

@keith-kaplan That's good to know. I was just following the script load order that we had on the AEM dev environment (view-source:https://dev.merative.com/resources/history).

Changes are up, can you take a look again? https://github.com/hlxsites/merative2/pull/251/commits/5bfebccb860e15869f2346e3490409239af85c00

[keith-kaplan]

Looks great. Thank you.

[venky-moonraft]

Looks good @proeung

[aem-code-sync[bot]]

Page	Scores	Audits	Google
/resources/history/index.html