fix(privacy-policy): Error resolved and scrolling padding added

[sahmad-merative]

Fixes #MERATIVE-860

Description

Added a table of contents with anchor links that jump down to each section in the page.

Adjusted offset position to align with column heading

Design Specs

If applicable, add the direct link to the design specs of the component/feature that's part of this PR.

• Figma Link - N/A

Test URLs

• Before (Changes from main): https://main--merative2--hlxsites.hlx.page/privacy
• After (Changes from this PR): https://860-privacy-policy--merative2--sahmad-merative.hlx.page/privacy

Testing Instruction

Franklin doc : https://merative.sharepoint.com/:w:/r/sites/Merative.comWebsite/_layouts/15/Doc.aspx?sourcedoc=%7B9a6326f1-8a50-461d-be6f-98bdf34d4a0a%7D&action=edit&wdPid=7612f173

[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
/privacy

[scottbridgeman]

@proeung - one question on the solution here and happy to talk through this if that's easier.

Just wondering about the URL structures. Please note: This is a true nit and I might be too picky on this one.

I noticed that the URL structure for the uses a #bookmark# - should we be using the bookmark number or the common section name in Word? I'm not sure if Franklin would allow for this, but it did jump out at me. Again, this is a nit and I'm not sure how the rest of the team would have the same feedback.

Happy to discuss if that's easier

vs.

[aem-code-sync[bot]]

Page	Scores	Audits	Google
/privacy

[proeung]

@scottbridgeman Thanks for the review and great question!

I noticed that the URL structure for the uses a #bookmark# - should we be using the bookmark number or the common section name in Word? I'm not sure if Franklin would allow for this, but it did jump out at me. Again, this is a nit and I'm not sure how the rest of the team would have the same feedback.

The # or anchor link should be pulled from the string of the Headline (eg. /privacy#children). I would double-check the hyperlink of the doc which has more options on the desktop app (see attached).

[aem-code-sync[bot]]

Page	Scores	Audits	Google
/privacy

[helms-charity]

@proeung if you use the full URL with the hash, I believe that will turn into the anchor link you want to use.

[proeung]

@helms-charity That's good to know, thanks! @scottbridgeman we might need to adjust the hyperlink setting of each link to include the full URL path as Charity mentioned above. In the meantime, I'm going to merge the changes in this PR and publish the existing changes made to this Privacy page (https://main--merative2--hlxsites.hlx.page/privacy) so that the error in the console is fixed via this PR.

[scottbridgeman]

@proeung - Perfect, thank you.