Refactor handbook-specific templates and style use
Why is this change being made?
The reason is twofold:
- All pages were previously loading unused styles that were intended to be specific to handbook pages
- The various handbook layout templates didn't explicitly load these handbook specific styles
A detailed audit of template, style, and JavaScript use is referenced in the related issue.
Before and after test samples:
-
handbook-page-toc
/handbook/about
Before After -
markdown_page
/pricing/premium
Before After -
default
/training
Before After -
release
/handbook/marketing/blog/release-posts
Before After -
job_family_page
/job-families/alliances/alliances-manager
Before After
Author Checklist
-
Provided a concise title for the MR -
Added a description to this MR explaining the reasons for the proposed change, per say-why-not-just-what -
Assign this change to the correct DRI - If the change relates to any part of the project other than updates to content and/or data files (e.g. team.yml) please make sure to ping
@gl-static-site-editor
in a comment for a review and merge. - If the DRI for the page/s being updated isn't immediate clear, then assign it to your manager.
- If your manager does not have merge rights, please ask someone to merge it AFTER it has been approved by your manager in #mr-buddies
- If the change relates to any part of the project other than updates to content and/or data files (e.g. team.yml) please make sure to ping
For help with failing pipelines reach out in #mr-buddies in Slack
Edited by Derek Knox