@dialpad/dialtone-vue 1.0.0-beta.test.4 → 1.0.0

package/README.md

@@ -1,6 +1,6 @@
-# Handset 📞
+# Dialtone Vue 📞
 
-Handset is a library of Vue components for [Dialtone][dt]. The goal is to simplify and standardize the use of common UI patterns and behaviour across all Dialpad projects.
+Dialtone Vue is a library of Vue components for [Dialtone][dt]. The goal is to simplify and standardize the use of common UI patterns and behaviour across all Dialpad projects.
 
 **[Component Documentation Site ↗️][handbook]**
 
@@ -8,31 +8,31 @@ Handset is a library of Vue components for [Dialtone][dt]. The goal is to simpli
 
 ### Project Status
 
-Handset is a new project, and as such it is under constant development as we add new components and refine existing ones. Please refer to the [project board][project] to see the status of Handset components and request new components that should be in the Handset library.
+Dialtone Vue is a new project, and as such it is under constant development as we add new components and refine existing ones. Please refer to the [project board][project] to see the status of Dialtone Vue components and request new components that should be in the Dialtone Vue library.
 
 [project]: https://github.com/orgs/dialpad/projects/1
 
 ### Timeline
 
-Our goal is to have a stable 1.0 release in early 2021. At this point, we will split Handset into a separate repository and follow semantic versioning.
+Our goal is to have a stable 1.0 release in Q3 2021. At this point, we will split Dialtone Vue into a separate repository and follow semantic versioning.
 
 ## Usage
 
-Handset components can be imported directly from the package. Some components also export named constants, which can be imported as well:
+Dialtone Vue components can be imported directly from the package. Some components also export named constants, which can be imported as well:
 
 ```js
-import { HsInput, VALIDATION_MESSAGE_TYPES } from '@dialpad/handset';
+import { DtInput, VALIDATION_MESSAGE_TYPES } from '@dialpad/dialtone-vue';
 ```
 
 ## Storybook Component Documentation
 
-Handset uses [Storybook][storybook] for documentation of components, as well as an environment for local development. Please see the [Storybook Documentation Site][handbook] for specific usage information and interactive documentation for each Handset component.
+Dialtone Vue uses [Storybook][storybook] for documentation of components, as well as an environment for local development. Please see the [Storybook Documentation Site][handbook] for specific usage information and interactive documentation for each Dialtone Vue component.
 
-All components in Handset should have stories written for them in Storybook. For more information on how to write stories, see the [documentation][stories].
+All components in Dialtone Vue should have stories written for them in Storybook. For more information on how to write stories, see the [documentation][stories].
 
 [storybook]: https://storybook.js.org
-[handbook]: https://static.dialpadcdn.com/storybook/index.html
-[stories]: https://static.dialpadcdn.com/storybook/index.html?path=/story/docs-storybook-getting-started--page
+[handbook]: https://dialtone-vue.netlify.app
+[stories]: https://dialtone-vue.netlify.app/?path=/story/docs-storybook-getting-started--page
 
 ### Running Storybook Locally
 
@@ -41,7 +41,7 @@ Storybook provides a sandbox to develop and experiment with components locally,
 To run Storybook locally, first install the dependencies:
 
 ```
-npm run install:storybook
+npm run storybook:install
 ```
 
 Then you can run the dev server:
@@ -50,55 +50,67 @@ Then you can run the dev server:
 npm run storybook
 ```
 
-## Developing Handset Components
+## Developing Dialtone Vue Components
 
-Building components for Handset is similar to components for Dialpad or UberConference, but there are some differences. Remember that Handset is a shared library so more care has to be taken to avoid breaking changes.
+Building components for Dialtone Vue is similar to components for Dialpad or UberConference, but there are some differences. Remember that Dialtone Vue is a shared library so more care has to be taken to avoid breaking changes.
 
-Remember that Handset is a separate project, so be sure to run the lint and unit tests for Handset separately whenever making changes to the library.
+Remember that Dialtone Vue is a separate project, so be sure to run the lint and unit tests for Dialtone Vue separately whenever making changes to the library.
 
 See [CONTRIBUTING](./CONTRIBUTING.md).
 
+### Project Setup
+
+#### NPM_AUTH_TOKEN
+
+Ensure that `NPM_AUTH_TOKEN` is set in your path. You will need to set the token to an NPM authentication token which has read level access to the `@dialpad` organization.
+
+#### Install Dependencies
+
+```bash
+npm install
+```
+
 ### CSS & Dialtone
 
-Dialtone components should utilize the global immutable CSS classes provided by Dialtone whenever possible. It is a requirement of any project using Handset to include these classes.
+Dialtone components should utilize the global immutable CSS classes provided by Dialtone whenever possible. It is a requirement of any project using Dialtone Vue to include these classes.
 
 If needed, you can also write custom CSS using the Dialtone LESS variables or mixins by importing `../css/dialtone.less`.
 
-Please **do not** use any scoped CSS in Handset components.
+Please **do not** use any scoped CSS in Dialtone Vue components.
 
 ### Unit Tests
 
-Each component should have a corresponding unit test in the `tests/specs` directory. There is no special test setup as Handset components do not have access to the Vuex store or custom methods/directives.
+Each component should have a corresponding unit test in the `tests/specs` directory. There is no special test setup as Dialtone Vue components do not have access to the Vuex store or custom methods/directives.
 
 ### Exports
 
-When adding a new component, please add its exports to `index.js`, including any named exports, so they're available for import to users of Handset:
+When adding a new component, please add its exports to `index.js`, including any named exports, so they're available for import to users of Dialtone Vue:
 
 ```js
 export {
-  default as HsInput,
-  INPUT_SIZE_TYPES,
+  default as DtInput,
+  INPUT_SIZES,
 } from './components/input.vue';
 ```
 
 ### External Dependencies
 
-Handset components are designed to be used in a variety of different projects. As such, Handset components should be pure Vue components with no dependencies on global Vue plugins or stores, except when noted below. This in particular means:
+Dialtone Vue components are designed to be used in a variety of different projects. As such, Dialtone Vue components should be pure Vue components with no dependencies on global Vue plugins or stores, except when noted below. This in particular means:
 
-- **No access to the Vuex store.** Different projects will have different store structures, and so Handset components cannot access the Vuex store. Handset components should take data as props only.
-- **No I18n.** Each project will have its own i18n implementation. Any text needed in a Handset component should be passed as props or slots.
-- **No custom directives.** Directives in Vue are installed globally and vary from project to project. Custom directives (such as `v-tooltip`) cannot be used in Handset components.
-- **No other custom global methods.** Some projects may implement custom global methods on the Vue object. Handset components are limited to the built-in Vue methods.
-- **No imports outside of the handset directory.**
-- **Vue 2 compatibility.** Handset components should ideally support Vue 2 and 3, but a minimum of Vue 2 support is currently required.
+- **No access to the Vuex store.** Different projects will have different store structures, and so Dialtone Vue components cannot access the Vuex store. Dialtone Vue components should take data as props only.
+- **No I18n.** Each project will have its own i18n implementation. Any text needed in a Dialtone Vue component should be passed as props or slots.
+- **No custom directives.** Directives in Vue are installed globally and vary from project to project. Custom directives (such as `v-tooltip`) cannot be used in Dialtone Vue components.
+- **No other custom global methods.** Some projects may implement custom global methods on the Vue object. Dialtone Vue components are limited to the built-in Vue methods.
+- **No imports outside of the dialtone-vue directory.**
+- **Vue 2 compatibility.** Dialtone Vue components should ideally support Vue 2 and 3, but a minimum of Vue 2 support is currently required.
 
-## Using Handset in your Project
+## Using Dialtone Vue in your Project
 
-Project using Handset should be aware of the requirements:
+Project using Dialtone Vue should be aware of the requirements:
 
-- Dialtone classes must be made available globally (to avoid duplication, Handset does not do this for you).
-- A tool like Webpack must be used to package the SFC components from Handset.
+- Dialtone classes must be made available globally (to avoid duplication, Dialtone Vue does not do this for you).
+- A tool like Webpack must be used to package the SFC components from Dialtone Vue.
 - LESS preprocessor support for Vue SFC `<style>` blocks.
-- Handset components are built for Vue 2, with Vue 3 support coming soon.
+- Dialtone Vue components are built for Vue 2, with Vue 3 support coming soon.
 
-These requirements are enforced via peerdependencies of Handset when possible.
+These requirements are enforced via peerdependencies of Dialtone Vue when possible.