pdap-design-system 1.0.0

package/CONTRIBUTING.md

@@ -0,0 +1,4 @@
+# Contributing
+For PDAP staff: 
+
+For the public: This is an internal system, but it could easily be forked and altered to meet your needs. Feel free to share potentially useful things back to us in a Pull Request.

package/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2023 Police Data Accessibility Project
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/README.md

@@ -0,0 +1,24 @@
+# Design System
+These are styling resources like CSS and templates for new PDAP microservices or branded web projects.
+
+Open `system/demo.html` to see how things look.
+`global-styles.css` are the styles used across all PDAP applications.
+`normalize.css` is used for more consistent cross-browser rendering.
+
+# Context
+We are making tools for transparency about a serious subject. We are be focused, friendly, and open.
+
+## Principles
+This is a first pass, so they're not etched in stone. Open to suggestions.
+
+- Our design should take accessibility seriously. 
+- Keep it simple: things should not do anything they don't need to do. 
+- We should keep our users informed and in control with timely, relevant feedback.
+- Things that look the same should behave in the same way, and an action should always produce the same result.
+- Don't reinvent the wheel: use standard conventions and cues.
+- Provide help to people in context, not in the docs.
+- Establish good visual hierarchy by ensuring each page and object has a primary function.
+
+## Assets
+Use these [brand assets](https://docs.pdap.io/meta/about/staff/brand-assets).
+Use this [terminology](https://docs.pdap.io/activities/terms-and-definitions).

package/docs/getting-started.md

@@ -0,0 +1,6 @@
+# Principles
+
+
+
+## Brand assets
+https://docs.pdap.io/meta/about/staff/brand-assets

package/package.json

@@ -0,0 +1,22 @@
+{
+  "name": "pdap-design-system",
+  "version": "1.0.0",
+  "description": "Global styles for PDAP apps",
+  "main": "system/css/global-styles.css",
+  "directories": {
+    "doc": "docs"
+  },
+  "scripts": {
+    "test": "echo \\\"No tests for CSS-only package.\\\" && exit 0"
+  },
+  "repository": {
+    "type": "git",
+    "url": "git+https://github.com/Police-Data-Accessibility-Project/design-system.git"
+  },
+  "author": "Police Data Accessibility Project, Inc.",
+  "license": "ISC",
+  "bugs": {
+    "url": "https://github.com/Police-Data-Accessibility-Project/design-system/issues"
+  },
+  "homepage": "https://github.com/Police-Data-Accessibility-Project/design-system#readme"
+}