GSA/sam-design-system-site

[Website]: Hosting the Standards on a sam.gov subdomain

Closed this issue · 1 comments

joshbruce commented

Issue type

  • Website

We use the standard GitHub pages methodology to build the Jekyll site. There were two folders being generated, or updated, for the US Web Design Standards that caused a lot of merge conflicts:

  1. The dist folder that held all the fonts, images, minified CSS, and minified JS.
  2. The assets folder that holds all the fonts, images, CSS, and JS for the jekyll site.

What we did to solve the problem on the US Web Design Standards was to host the Standards site (standards.usa.gov) to cloud.gov, have the platform perform the build of the Jekyll site via web hooks and a checkout, and (I believe) part of that CI process creates the dist folder and pushes directly to the master branch. All of that allowed us to ignore both the dist and assets folders.

Could we do something similar on one of the platforms?

standards.sam.gov and standards-staging.sam.gov

Tagging: @BrianGilmanGSA, and @pammiller0

joshbruce commented

The proposed domains would be:

https://standards.sam.gov - this would basically take the gh-pages or a yet to be created master branch - and do a Jekyll build via Gulp tasks; thereby, allowing us to ignore a lot of files and reduce the possibility of merge conflicts.

https://standards-staging.sam.gov - this would use the gh-pages-staging or develop - and allow developers to see the upcoming changes via an actual site build as opposed to having to wait or view on their local machines.