diff --git a/.circleci/config.yml b/.circleci/config.yml new file mode 100644 index 00000000..41e253bd --- /dev/null +++ b/.circleci/config.yml @@ -0,0 +1,34 @@ +version: 2 +jobs: + build: + docker: + - image: circleci/ruby:2.6-node-browsers-legacy + steps: + - checkout + - restore_cache: + keys: + - v2-npm-{{ checksum "package-lock.json" }} + - v2-npm- + - run: npm install + - save_cache: + key: v2-npm-{{ checksum "package-lock.json" }} + paths: + - node_modules + - restore_cache: + keys: + - v2-bundle-{{ checksum "Gemfile.lock" }} + - v2-bundle- + - run: bundle install --path vendor/bundle + - save_cache: + key: v2-bundle-{{ checksum "Gemfile.lock" }} + paths: + - vendor/bundle + - run: npm run build + - run: npm run test + + +workflows: + version: 2 + commit: + jobs: + - build diff --git a/.dependabot/config.yml b/.dependabot/config.yml new file mode 100644 index 00000000..643706c2 --- /dev/null +++ b/.dependabot/config.yml @@ -0,0 +1,8 @@ +version: 1 +update_configs: + - package_manager: "ruby:bundler" + directory: "/" + update_schedule: "weekly" + - package_manager: "javascript" + directory: "/" + update_schedule: "weekly" diff --git a/.gitattributes b/.gitattributes new file mode 100644 index 00000000..1a6bd458 --- /dev/null +++ b/.gitattributes @@ -0,0 +1 @@ +package-lock.json binary diff --git a/.gitignore b/.gitignore new file mode 100644 index 00000000..238c9a33 --- /dev/null +++ b/.gitignore @@ -0,0 +1,6 @@ +_site +.sass-cache +.jekyll-metadata +node_modules +.bundle +.jekyll-cache/ diff --git a/.ruby-version b/.ruby-version new file mode 100644 index 00000000..338a5b5d --- /dev/null +++ b/.ruby-version @@ -0,0 +1 @@ +2.6.6 diff --git a/404.html b/404.html new file mode 100644 index 00000000..536f4fb2 --- /dev/null +++ b/404.html @@ -0,0 +1,11 @@ +--- +layout: default +permalink: /404.html +--- + +
The requested page could not be found (404).
+Support the callout with some short explanatory text. You don’t need more than a couple of sentences.
+ Call to action +Graphic headings can be used a few different ways, depending on what your landing page is for. Highlight + your values, specific program areas, or results.
+Keep body text to about 30 words. They can be shorter, but try to be somewhat balanced across all four. It + creates a clean appearance with good spacing.
+For anything you want to highlight here, understand what your users know now, and what activity or + impression you want from them after they see it.
+In addition to your goal, find out your users’ goals. What do they want to know or do that supports your + mission? Use these headings to show those.
+The tagline should inspire confidence and interest, focusing on the value that your overall approach offers to your audience. Use a heading typeface and keep your tagline to just a few words, and don’t confuse or mystify.
+Use the right side of the grid to explain the tagline a bit more. What are your goals? How do you do your work? Write in the present tense, and stay brief here. People who are interested can find details on internal pages.
+_config.yml
and look for searchgov
fieldsaffiliate
and access_key