This project is a work in progress and should be considered as a DRAFT.
**_This playbook is NOT a source of authoritative, legal, or regulatory guidance and has not been officially endorsed by the Center for Medicaid and CHIP Services (CMCS) or the Food and Nutrition Service (FNS). State agencies should follow the federal agency's regulations for your federally-funded state-administered program.
This content is advisory only and should be adapted appropriately for each state and scenario. Ultimately, it is the responsibility of state Medicaid and Supplemental Nutrition Assistance Program (SNAP) officials to ensure that implementation of any project is compliant with federal Medicaid and SNAP statute and regulations. Refer to CMS’ and FNS’ website for up-to-date official guidance. _**
Refer to CMCS' website and FNS' website for up-to-date official guidance.
This project is being developed by Nava in collaboration with USDS.
The Authentication & Account Creation (AAC) Playbook aims to help state program delivery and IT teams to
- Understand and demystify federal guidance on authentication and digital account creation
- Have informed conversations to identify approaches to authentication and digital account creation that balance usability, security, reliability, and equity for applicants applying for and accessing their SNAP and Medicaid benefits.
In this playbook, you’ll find:
- Recommended best practices
- Common terms and plain language definitions
- Example language and visual templates for authN and account creation
Following this guidance can improve application form accessibility, equity, and usability.
The following guide is for members of the project team who have access to the repository. The AAC Playbook uses a modified fork of the Just The Docs Jekyll theme. Instructions for local development are below.
A video walkthrough of various Just the Docs features
just-the-docs-features-walkthrough.mp4
The Just the Docs Template provides the simplest, quickest, and easiest way to create a new website that uses the Just the Docs theme. To get started with creating a site, just click "use the template"!
Note: To use the theme, you do not need to clone or fork the Just the Docs repo! You should do that only if you intend to browse the theme docs locally, contribute to the development of the theme, or develop a new theme based on Just the Docs.
You can easily set the site created by the template to be published on GitHub Pages – the template README file explains how to do that, along with other details.
If Jekyll is installed on your computer, you can also build and preview the created site locally. This lets you test changes before committing them, and avoids waiting for GitHub Pages.1 And you will be able to deploy your local build to a different platform than GitHub Pages.
More specifically, the created site:
- uses a gem-based approach, i.e. uses a
Gemfileand loads thejust-the-docsgem - uses the GitHub Pages / Actions workflow to build and publish the site on GitHub Pages
Other than that, you're free to customize sites that you create with the template, however you like. You can easily change the versions of just-the-docs and Jekyll it uses, as well as adding further plugins.
Alternatively, you can install the theme as a Ruby Gem, without creating a new site.
Add this line to your Jekyll site's Gemfile:
gem "just-the-docs"And add this line to your Jekyll site's _config.yml:
theme: just-the-docsAnd then execute:
$ bundle
Or install it yourself as:
$ gem install just-the-docs
Alternatively, you can run it inside Docker while developing your site
$ docker-compose up
View the documentation for usage information.
Bug reports, proposals of new features, and pull requests are welcome on GitHub at https://github.com/just-the-docs/just-the-docs. This project is intended to be a safe, welcoming space for collaboration, and contributors are expected to adhere to the Contributor Covenant code of conduct.
- Submit an Issue that motivates the changes, using the appropriate template
- Discuss the proposed changes with other users and the maintainers
- Open a Pull Request
- Ensure all CI tests pass
- Provide instructions to check the effect of the changes
- Await code review
- As few dependencies as possible
- No build script needed
- First class mobile experience
- Make the content shine
To set up your environment to develop this theme: fork this repo, the run bundle install from the root directory.
A modern devcontainer configuration for VSCode is included.
Your theme is set up just like a normal Jekyll site! To test your theme, run bundle exec jekyll serve and open your browser at http://localhost:4000. This starts a Jekyll server using your theme. Add pages, documents, data, etc. like normal to test your theme's contents. As you make modifications to your theme and to your content, your site will regenerate and you should see the changes in the browser after a refresh, just like normal.
When this theme is released, only the files in _layouts, _includes, and _sass tracked with Git will be included in the gem.
The theme is available as open source under the terms of the MIT License.
