search

department-of-veterans-affairs / va.gov-team

Public resources for building on and in support of VA.gov. Visit complete Knowledge Hub:
https://depo-platform-documentation.scrollhelp.site/index.html
284 stars 206 forks source link

Evaluate the vagov-content repo #24995

Open timwright12 opened 3 years ago

timwright12 commented 3 years ago

No one seems to use this repo https://github.com/department-of-veterans-affairs/vagov-content

Are we able to sunset it? Even if that means moving some of the content into Drupal. Let's look into it and see.

mchelen-gov commented 3 years ago

it's still used for certain types of content, see https://github.com/department-of-veterans-affairs/va.gov-team/issues/26991 for one example (which would be nice to get moved into CMS)

laineymajor commented 2 years ago

repo filled with markdown files. need collaboration with cms.

timwright12 commented 2 years ago

@mchelen-gov Official ownership of this repo seems unclear; should it be officially assigned to Platform CMS or remain with Release Tools?

mchelen-gov commented 2 years ago

@mchelen-gov Official ownership of this repo seems unclear; should it be officially assigned to Platform CMS or remain with Release Tools?

I would ask the PCMS team if they want to assume ownership?

timcosgrove commented 2 years ago

Have there been active support requests connected to this?

Retiring this repo is in our longer-term plans. Since we are looking to sunset Metalsmith / content-build, and this repo is built by content-build, some sort of migration does need to happen.

mchelen-gov commented 2 years ago

Have there been active support requests connected to this?

Retiring this repo is in our longer-term plans. Since we are looking to sunset Metalsmith / content-build, and this repo is built by content-build, some sort of migration does need to happen.

I'm honestly unsure if/how this repo is used in the current content build process, even within the context of Metalsmith usage 🤷

timwright12 commented 2 years ago

The current build process runs through the markdown files before it pings Drupal in this repo and creates static pages from them in https://github.com/department-of-veterans-affairs/vagov-content/tree/main/pages

We have been maintaining this repo, there isn't much going on with it, but we did recently spend time converting it to github actions and there are some PR reviews every so often. App teams who need content pages still use it (last update 12 days ago). In my opinion, it would just be a few hours work (if that) to migrate the content into Drupal, delete it from the repo, and contact the content owners.

The only functionality in the repo is the banner fragment https://github.com/department-of-veterans-affairs/vagov-content/tree/main/fragments/home that public websites used to push emergency information to the website, but I'm not sure if that's use anymore either.

It would be really great if Platform CMS could either quickly migrate content out of this system so we can sunset the repo or just take ownership

timcosgrove commented 2 years ago

We'll assume ownership, with the explicit aim of migrating the content to the CMS or otherwise replacing it or retiring it, and then sunsetting the repo.

timwright12 commented 2 years ago

@timcosgrove awesome, thanks!

laineymajor commented 2 years ago

Thanks @timcosgrove ! I'm assigning this to you right now. You can then reassign as you'd like.

laineymajor commented 2 years ago

@timcosgrove I can transfer this ticket over to you.