Skip to content

Investigate Lovell and next-build #20572

Open
@laflannery

Description

@laflannery

Background

Lovell is a non-typical VAMC System in that it also serves active duty service members, not just Veterans. The Lovell Initiative brief gives some more detailed background information about this.

The Sitewide team built the Lovell System and the logic for this within content-build and launched in 2023.

Lovell documentation and info

Sitewide contacts

For direct assistance, questions from Sitewide, the best contacts for help would probably be:

  • Eli Selkin for Front end questions
  • Christian Burk for Drupal questions

Description

Issues have been found with the Lovell pages on the templates that have already been migrated to next-build. However, it is unclear if these issues need to be solved one at a time or if the overall Lovell logic needs to be address and looked at more holistically in order to be sure that all of Lovell will work properly as more templates get migrated.

We want to investigate the current issues that have been found, look at how Lovell works and is implemented in content-build and then compare that to how this was implemented in next-build.

Existing next-build issues

These are existing issues in next build that have already been found, however what we want to investigate is - are these part of a larger issue and if we fix the logic as a whole all of these issues might magically get resolved as well? Or are they really all 6 individual issues and should be resolved as 6 individual issues? We don't necessarily have to solve them within the scope of this ticket but just to et a sense of what might be going on

Acceptance Criteria

  • Lovell logic is next-build is investigated and compared to content-build
  • Lovell issues mentioned above are investigated to determine if they seem to be one-off issues or if there might be a larger issue with the Lovell logic in general
  • A general plan of attack to correct the issues is determined if the individual tickets above are not sufficient

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

CMS TeamCMS Product team that manages both editor exp and devopsnext-buildFE Repository that will replace content-build. Uses NextJS, builds static pages.

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions