Skip to content

Issues: department-of-veterans-affairs/va.gov-cms

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Author
Filter by author
Loading
Label
Filter by label
Loading
Use alt + click/return to exclude labels
or + click/return for logical OR
Projects
Filter by project
Loading
Milestones
Filter by milestone
Loading
Assignee
Filter by who’s assigned
Sort

Issues list

[Epic][AP] Migrate all page layouts Accelerated Publishing Epic Issue type Needs refining Issue status
#17701 opened Apr 2, 2024 by timcosgrove
8 of 36 tasks
Next-Build CI should fail if Jest code-coverage is below 80% Accelerated Publishing CMS Team CMS Product team that manages both editor exp and devops Needs refining Issue status next-build FE Repository that will replace content-build. Uses NextJS, builds static pages. Operational stability
#17631 opened Mar 26, 2024 by timcosgrove
Tugboat Next.js server can be restarted via Composer command Accelerated Publishing CMS Team CMS Product team that manages both editor exp and devops
#17400 opened Mar 4, 2024 by alexfinnarn Draft
2 of 19 tasks
Uptime monitoring and alert for CMS Prod Preview server Accelerated Publishing CMS Team CMS Product team that manages both editor exp and devops Content preview [CMS feature] Content as it appears on va.gov DevOps CMS team practice area Needs refining Issue status
#16954 opened Jan 22, 2024 by timcosgrove
component: node--health_care_local_health_service (VAMC Facility Health Service) Accelerated Publishing Facilities Facilities products (VAMC, Vet Center, etc) Needs refining Issue status sitewide VA.gov frontend CMS team practice area VAMC CMS managed product owned by Facilities team
#16797 opened Jan 10, 2024 by timcosgrove
1 task
layout: node--health_care_local_facility (VAMC Facility) Accelerated Publishing Facilities Facilities products (VAMC, Vet Center, etc) Needs refining Issue status sitewide VA.gov frontend CMS team practice area VAMC CMS managed product owned by Facilities team
#16795 opened Jan 10, 2024 by timcosgrove
component: node--health_care_local_facility (VAMC Facility) Accelerated Publishing Facilities Facilities products (VAMC, Vet Center, etc) Needs refining Issue status sitewide VA.gov frontend CMS team practice area VAMC CMS managed product owned by Facilities team
#16793 opened Jan 10, 2024 by timcosgrove
1 task
layout: node--vamc_system_policies_page (VAMC System Policies Page) Accelerated Publishing Facilities Facilities products (VAMC, Vet Center, etc) Needs refining Issue status sitewide VA.gov frontend CMS team practice area VAMC CMS managed product owned by Facilities team
#16763 opened Jan 8, 2024 by timcosgrove
layout: node--vamc_operating_status_and_alerts (VAMC System Operating Status) Accelerated Publishing Facilities Facilities products (VAMC, Vet Center, etc) Needs refining Issue status sitewide VA.gov frontend CMS team practice area VAMC CMS managed product owned by Facilities team
#16760 opened Jan 8, 2024 by timcosgrove
1 task
layout: node--health_care_region_page (VAMC System) Accelerated Publishing Facilities Facilities products (VAMC, Vet Center, etc) Needs refining Issue status sitewide VA.gov frontend CMS team practice area VAMC CMS managed product owned by Facilities team
#16758 opened Jan 8, 2024 by timcosgrove
1 task
component: paragraph--situation_update (Situation update) Accelerated Publishing Facilities Facilities products (VAMC, Vet Center, etc) Needs refining Issue status sitewide VA.gov frontend CMS team practice area VAMC CMS managed product owned by Facilities team
#16753 opened Jan 8, 2024 by timcosgrove
1 task
component: paragraph--service_location_address (Service location address) Accelerated Publishing Facilities Facilities products (VAMC, Vet Center, etc) Needs refining Issue status sitewide VA.gov frontend CMS team practice area VAMC CMS managed product owned by Facilities team
#16752 opened Jan 8, 2024 by timcosgrove
1 task
component: paragraph--service_location (Service Location) Accelerated Publishing Facilities Facilities products (VAMC, Vet Center, etc) Needs refining Issue status next-build FE Repository that will replace content-build. Uses NextJS, builds static pages. sitewide VA.gov frontend CMS team practice area VAMC CMS managed product owned by Facilities team
#16751 opened Jan 8, 2024 by timcosgrove
1 task
component: paragraph--magichead_group (Overview section) Accelerated Publishing Needs refining Issue status Public Websites Scrum team in the Sitewide crew Resources and support CMS managed product owned by Public Websites team
#16750 opened Jan 8, 2024 by timcosgrove
1 task
component: paragraph--lists_of_links (Lists of links) Accelerated Publishing Facilities Facilities products (VAMC, Vet Center, etc) Needs refining Issue status Public Websites Scrum team in the Sitewide crew Resources and support CMS managed product owned by Public Websites team VAMC CMS managed product owned by Facilities team
#16747 opened Jan 8, 2024 by timcosgrove
1 task
component: paragraph--health_care_local_facility_servi (Facility location support service) Accelerated Publishing Facilities Facilities products (VAMC, Vet Center, etc) Needs refining Issue status next-build FE Repository that will replace content-build. Uses NextJS, builds static pages. sitewide VA.gov frontend CMS team practice area VAMC CMS managed product owned by Facilities team
#16746 opened Jan 8, 2024 by timcosgrove
1 task
layout: node--health_care_region_detail_page (VAMC Detail Page) Accelerated Publishing Facilities Facilities products (VAMC, Vet Center, etc) Needs refining Issue status next-build FE Repository that will replace content-build. Uses NextJS, builds static pages. sitewide VA.gov frontend CMS team practice area VAMC CMS managed product owned by Facilities team
#16722 opened Jan 5, 2024 by timcosgrove
1 task
layout: node--publication_listing (Publication Listing Page) Accelerated Publishing Needs refining Issue status Public Websites Scrum team in the Sitewide crew Resources and support CMS managed product owned by Public Websites team
#16630 opened Jan 2, 2024 by timcosgrove
1 task
layout: node--nca_facility (NCA Facility) Accelerated Publishing Facilities Facilities products (VAMC, Vet Center, etc) NCA for NCA facilities that are not cemeteries Needs refining Issue status
#16624 opened Jan 2, 2024 by timcosgrove
1 task
layout: node--health_services_listing (Health Services List) Accelerated Publishing Facilities Facilities products (VAMC, Vet Center, etc) Needs refining Issue status next-build FE Repository that will replace content-build. Uses NextJS, builds static pages. sitewide VA.gov frontend CMS team practice area VAMC CMS managed product owned by Facilities team
#16618 opened Jan 2, 2024 by timcosgrove
1 task
layout: node--campaign_landing_page (Campaign Landing Page) Accelerated Publishing Needs refining Issue status Public Websites Scrum team in the Sitewide crew Resources and support CMS managed product owned by Public Websites team
#16603 opened Jan 2, 2024 by timcosgrove
1 task
[Epic][AP] Next Build content deploy pipeline Accelerated Publishing CMS Team CMS Product team that manages both editor exp and devops DevOps CMS team practice area Epic Issue type Needs refining Issue status next-build FE Repository that will replace content-build. Uses NextJS, builds static pages.
#15952 opened Nov 1, 2023 by timcosgrove AP: Milestone 2
Spike: local development environments for Next-Build Accelerated Publishing CMS Team CMS Product team that manages both editor exp and devops next-build FE Repository that will replace content-build. Uses NextJS, builds static pages.
#14420 opened Jul 19, 2023 by timcosgrove
2 tasks
layout: node--page (Benefits Detail Page) Accelerated Publishing Public Websites Scrum team in the Sitewide crew Resources and support CMS managed product owned by Public Websites team
#14368 opened Jul 14, 2023 by timcosgrove
1 task
ProTip! Follow long discussions with comments:>50.