Huge News!Announcing our $40M Series B led by Abstract Ventures.Learn More
Socket
Sign inDemoInstall
Socket

@cmsgov/ds-healthcare-gov

Package Overview
Dependencies
Maintainers
1
Versions
169
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

@cmsgov/ds-healthcare-gov - npm Package Compare versions

Comparing version 1.0.0 to 1.0.1-beta.1

.babelrc

34

package.json
{
"name": "@cmsgov/ds-healthcare-gov",
"version": "1.0.0",
"version": "1.0.1-beta.1",
"publishConfig": {

@@ -8,3 +8,33 @@ "access": "public"

"description": "A Design System companion for HealthCare.gov",
"repository": "https://github.cms.gov/CMS-WDS/ds-healthcare-gov"
"repository": "https://github.cms.gov/CMS-WDS/ds-healthcare-gov",
"scripts": {
"lint": "stylelint 'src/**/*.scss' && eslint --ext .jsx --ext .js src/"
},
"main": "dist/index.js",
"dependencies": {
"classnames": "^2.0.0",
"i18next": "^10.0.0",
"react-i18next": "^7.0.0"
},
"devDependencies": {
"@cmsgov/design-system-core": "^1.10.0",
"@cmsgov/design-system-layout": "^1.10.0",
"@cmsgov/design-system-support": "^1.10.0",
"@cmsgov/eslint-config-design-system": "^1.3.0",
"@cmsgov/stylelint-config-design-system": "^1.1.0",
"babel-plugin-transform-object-assign": "^6.22.0",
"babel-preset-es2015": "^6.24.1",
"babel-preset-react": "^6.24.1",
"eslint": "^4.16.0",
"eslint-config-nava": "^2.1.0",
"react": "^16.2.0",
"react-dom": "^16.2.0",
"stylelint": "^8.4.0",
"whatwg-url": "^6.4.0"
},
"peerDependencies": {
"@cmsgov/design-system-core": "^1.10.0",
"@cmsgov/design-system-layout": "^1.10.0",
"@cmsgov/design-system-support": "^1.10.0"
}
}

62

README.md

@@ -1,12 +0,20 @@

# HealthCare.gov Site Package
> A Site Package is a method for sharing common, site-specific, design and code resources between the various teams working on HealthCare.gov. These resources are unique to HealthCare.gov, and not generalized for inclusion in the [Design System](https://github.com/cmsgov/design-system). It includes assets like design system overrides and site-specific components.
A Site Package is a method for sharing common, site-specific, design and code resources between the various teams working on HealthCare.gov. These resources are unique to HealthCare.gov, and not generalized for inclusion in the [Design System](https://github.com/cmsgov/design-system).
[![npm](https://img.shields.io/npm/v/@cmsgov/ds-healthcare-gov.svg?label=@cmsgov%2Fds-healthcare-gov)](https://www.npmjs.com/package/@cmsgov/ds-healthcare-gov)
## Usage
### Sass
### Installation
Import the Site Package's Sass files _before_ you import the design system. For example:
1. [Install the design system](https://design.cms.gov/getting-started/#installation)
2. Install the site package:
```
npm install --save @cmsgov/ds-healthcare-gov
```
```sass
### Import Sass
The source files included are written in Sass (`.scss`). You can add your `node_modules` directory to your Sass [`includePaths`](https://github.com/sass/node-sass#includepaths) and import the file like this, making sure to **import the Site Package's file _before_ you import the design system**:
```scss
@import '@cmsgov/ds-healthcare-gov/src/index';

@@ -16,9 +24,35 @@ @import '@cmsgov/design-system-core/src/index';

## Context
## Contributing
HealthCare.gov consists of multiple codebases maintained by different teams. App 2.0 lives in one repo maintained by Nava, Window Shop lives in a different repo maintained by Ad Hoc, and Plan Compare lives in yet another repo. Currently this means some design assets and code are duplicated across codebases, going against the software development principle to keep things [DRY](https://en.m.wikipedia.org/wiki/Don%27t_repeat_yourself). These multiple codebases naturally tend to have differences, and as a result have caused inefficiencies and inconsistencies to creep into the user interface.
Please view the [CONTRIBUTING.md](CONTRIBUTING.md) to read how you can add to the site package, as well as how to preview the site package in the context of the design system's documentation site.
## File structure
```
├── dist
│   └── index.css Compiled CSS
├── src
   ├── components
   │   ├── Header
   │   │   ├── Header.jsx Top-level <Header> component
   │   │   ├── defaultMenuLinks.js Default menu links for each header variation
   │   └── index.scss Component Sass imports
   ├── locale
   │   ├── en.json English i18n strings
   │   ├── es.json Spanish i18n strings
   │   └── translate.js react-i18next initializer and HOC
   ├── index.scss Main Sass entry point with all imports
   └── settings
   └── _override.color.scss Design system color variable overrides
```
---
## Why a site package?
HealthCare.gov consists of multiple codebases maintained by different teams. App 3.0 lives in one repo maintained by Nava, Window Shop lives in a different repo maintained by Ad Hoc, and Plan Compare lives in yet another repo. Currently this means some design assets and code are duplicated across codebases, going against the software development principle to keep things [DRY](https://en.m.wikipedia.org/wiki/Don%27t_repeat_yourself). These multiple codebases naturally tend to have differences, and as a result have caused inefficiencies and inconsistencies to creep into the user interface.
The Design System is one way we're addressing the issues mentioned above. However, the design system is meant to be used by many CMS (Centers for Medicare & Medicaid Services) websites, not just HealthCare.gov. As a result, the resources within the design system are not tied to a particular website.
## Goals
### Goals

@@ -29,10 +63,10 @@ The primary goal of the Site Package is to reduce the amount of duplicate instances of HealthCare.gov front-end components and design assets, and having a single source of truth which all teams can contribute to and use.

### Non-goals
#### Non-goals
- The Site Package is not meant to be as robust or as large as the Design System. It should be as small as possible, and ideally all reusable components would be from the design system.
- The Site Package is not meant to serve as a resource for best practices or accessibility guidelines — that's the responsibility of the design system.
- The HealthCare.gov Site Package is not meant to be a solution for other CMS websites.
* The Site Package is not meant to be as robust or as large as the Design System. It should be as small as possible, and ideally all reusable components would be from the design system.
* The Site Package is not meant to serve as a resource for best practices or accessibility guidelines — that's the responsibility of the design system.
* The HealthCare.gov Site Package is not meant to be a solution for other CMS websites.
## Additional links
### Additional links
- [The original tech spec for Site Packages can be viewed in the Design System Confluence](https://confluence.cms.gov/pages/worddav/preview.action?fileName=2017.06.21.E+-+Tech+spec+HealthCare.gov+Site+Package.pdf&pageId=65409149)
* [The original tech spec for Site Packages can be viewed in the Design System Confluence](https://confluence.cms.gov/pages/worddav/preview.action?fileName=2017.06.21.E+-+Tech+spec+HealthCare.gov+Site+Package.pdf&pageId=65409149)

Sorry, the diff of this file is not supported yet

SocketSocket SOC 2 Logo

Product

  • Package Alerts
  • Integrations
  • Docs
  • Pricing
  • FAQ
  • Roadmap
  • Changelog

Packages

npm

Stay in touch

Get open source security insights delivered straight into your inbox.


  • Terms
  • Privacy
  • Security

Made with ⚡️ by Socket Inc