vets-website

Hi! Can you elaborate on what in particular on the VA site that causes serious harm to the people it's meant to serve? I'm happy to bring it to the team or if you don't feel comfortable with stating it here, please bring it up to the open source website for va.gov. https://github.com/department-of-veterans-affairs/vets-websi...

Vercel is all proprietary/closedsource right, just Next.js is opensource right? Truly asking/wondering, not making a statement or trying to attack, just getting clarity? I ask because I work on VA.gov which requires FedRamped SaaS and PaaS OR on-premise installs and I don't think Vercel has either but we could use some parts of Vercel as on-prem if there were a paid on-prem support system. VA.gov right now is a static build system (Metalsmith + Liquid templates) stored in an S3 bucket that we are working on moving to Next.js. Here are the open source repos that make up VA.gov: https://github.com/department-of-veterans-affairs/content-bu... https://github.com/department-of-veterans-affairs/vets-websi... https://github.com/department-of-veterans-affairs/va.gov-cms

There is a start on VA.gov already happening in this direction. The front-end codebase and backend (Drupal 8) CMS are both fully opensource for VA.gov. * Frontend - https://github.com/department-of-veterans-affairs/vets-websi... * Backend - https://github.com/department-of-veterans-affairs/va.gov-cms... Paul's company is working on this project too (whom I work alongside with but with a different company)! The U.S. Digital Service is really a big factor in this, see the playbook, specifically play 13: > If the codebase has not been released under an open source license, explain why. source: https://playbook.cio.gov/#play13. So, see how this is now flipped. It is now "hey, you need to open source this by default, and if not, you need to explain why you didn't." and not the other way around! Update: See Andrew Gunsch's comment in this threa

Alrighty, after tinkering yesterday an opportunity came up to use this for real work! And helped us mock testing for a bad JSON response we are seeing on a remote server, but mocked it locally for better error logging. (gave shoutout to HTTP Toolkit here > https://github.com/department-of-veterans-affairs/vets-websi...) This just earned a subscription, will get it processed soon! Thanks again, a breeze to use!

https://github.com/department-of-veterans-affairs/vets-websi... :-)