NFR: Prepare for migration
Opened this issue · 0 comments
alexiscoelho commented
Context/Description
Adobe AC:
@dkuntze:
- Set up the new repository for the Mack migration
- Remove static configs (helix-query.yaml, helix-sitemap.yaml and robots.txt)
- Release
Frontend AC:
@alexiscoelho:
- Give permissions to the team to the new repo
- Copy labels to the new repo
- Do necessary doc changes
- Remove hard coded market code
- Remove and refactor hardcoded references to
macktrucks.com
- Remove and refactor hardcoded references to
macktrucks-com
- Review generation of the Atom Feed
- Ask for and if possible remove all files under the folder
files
- Test i18N configs
- Remove config-patches (.patch)
- Test deployment on
main
Dev NOTES:
Remove hardcoded urls in:
- .github/ci/generate-news-feed.js
- blocks/breadcrumb/breadcrumb.js
- blocks/eloqua-form/forms/buy-mack-request-a-quote.html
- blocks/eloqua-form/forms/contact-us.html
- blocks/eloqua-form/forms/subscribe.html
- scripts/scripts.js
- 404.html
The generations of the Atom Feed (feed.xml) will be needed to do some changes:
- Generate multiple xml files per location
- Refactor and adapt the configurations and generation of the files at:
.github/ci/generate-news-feed.js
- Reconfigure the workflow to fit the needs:
.github/workflows/generate-atom-news-feeds.yaml
- Check the feed configurations on the header to ensure the browser extensions can pick up the feed, we might be missing configs there
blocks/dealer-locator/sidebar-maps.js
- Investigate the hardcoded
https://www.macktrucks.com/simpleprox.ashx
urls
Acceptance Criteria
User AC:
The website should work as before
Editor AC:
Specific market configurations should be done on Sharepoint
Non-functional AC:
The website should work as expected