We need to understand the impact of hardcoded logic in custom pages now that cms-export is no longer a consideration. Some pages seem to be disconnected (as described in [#16830]. Similar work was done to remove legacy logic from the health services page
Logic in src/site/stages/build/drupal/health-care-region.js handles past event pages which don't (and probably can't) correspond to a drupal content type so will need to be retained
/status will be deprecated
Tasks
[ ] Review the custom pages in src/site/stages/build/drupal/health-care-region.js, /status, /locations
[ ] Detemine:
Are the pages are still needed?
If so, is the code necessary?
Or overriding the Drupal content?
Acceptance Criteria
[ ] Recommendations for resolveing the hard coded logic and technical debt on src/site/stages/build/drupal/health-care-region.js, /status, /locations_
Issue Description
We need to understand the impact of hardcoded logic in custom pages now that cms-export is no longer a consideration. Some pages seem to be disconnected (as described in [#16830]. Similar work was done to remove legacy logic from the health services page
src/site/stages/build/drupal/health-care-region.js
handles past event pages which don't (and probably can't) correspond to a drupal content type so will need to be retained/status
will be deprecatedTasks
src/site/stages/build/drupal/health-care-region.js
,/status
,/locations
Acceptance Criteria
src/site/stages/build/drupal/health-care-region.js
,/status
,/locations
_