3.3.9 • Published 6 days ago

@commercetools-docs/writing-style v3.3.9

Weekly downloads
484
License
MIT
Repository
github
Last release
6 days ago

commercetools Writing Style Linter

This package provides

  • commercetools specific writing style and terminology rules for the configurable vale prose linter.
  • the commercetools-vale command line tool which wraps a bundled vale build and calls it using the included writing style and configuration

The base style is the Google Developer Documentation Style Guide, which is included as a copy (MIT licensed, too) and modified and enriched with commercetools specific rules.

The configuration defaults to checking .md, .mdx, .txt, and .html files, which can be overridden by calling it with a command-line parameter commercetools-vale --glob='*.{js,md}' ./path/to/content passing a list of supported file format extensions.

As of Nov 2019, basing off Google's styles was a pragmatic choice. Other styles like Microsoft's are attractive starting points, too.

Linter Usage: Standalone command-line

  1. Install the command globally via yarn global add @commercetools-docs/writing-style or npm install -g @commercetools-docs/writing-style
  2. Use it by calling commercetools-vale ./path/to/your/content

Please don't forget to frequently update the package to get the latest styles.

Linter Usage: In Editor plugins

In addition, you can install a matching editor plugin to get immediate feedback while authoring. If your plugin allows, reconfigure the command from vale to commercetools-vale.

The plugin for VSCode does not support such configuration yet.

Linter Usage: CI and command line in Javascript Projects

  1. Add the writing-style package as a development dependency: yarn add --dev @commercetools-docs/writing-style
  2. In your project's folder, call it from the command line via npx commercetools-vale ./your/path/to/content and optionally add vale command line parameters as needed (for example --no-wrap on command line jobs).
    • Tip: Running it over your complete repository is not a good idea since it checks the complete node_modules folder which takes a long time and is not your content.

Contributing

All contributions, especially to enrich and complete the commercetools specific terminology and branding are welcome.

Please always provide content examples in the pull request to explain the rationale and typical use cases.

3.3.9

28 days ago

3.3.8

4 months ago

3.3.7

5 months ago

3.3.6

11 months ago

3.3.5

1 year ago

3.3.4

1 year ago

3.3.3

1 year ago

3.3.1

2 years ago

3.3.2

1 year ago

3.3.0

2 years ago

3.2.0

2 years ago

3.1.1

2 years ago

3.1.0

2 years ago

3.0.12

2 years ago

3.0.9

2 years ago

3.0.10

2 years ago

3.0.11

2 years ago

3.0.8

2 years ago

3.0.7

3 years ago

3.0.6

3 years ago

3.0.5

3 years ago

3.0.4

3 years ago

3.0.3

3 years ago

3.0.2

4 years ago

3.0.1

4 years ago

3.0.1-canary.6

4 years ago

3.0.1-canary.5

4 years ago

3.0.1-canary.4

4 years ago

3.0.1-canary.2

4 years ago

3.0.1-canary.1

4 years ago

3.0.1-canary.3

4 years ago

3.0.0

4 years ago

3.0.1-canary.0

4 years ago

2.5.1-canary.27

4 years ago

2.5.1-canary.26

4 years ago

2.5.1-canary.25

4 years ago

2.5.1-canary.24

4 years ago

2.5.1-canary.23

4 years ago

2.5.1-canary.21

4 years ago

2.5.1-canary.20

4 years ago

2.5.1-canary.19

4 years ago

2.5.1-canary.18

4 years ago

2.5.1-canary.17

4 years ago

2.5.1-canary.15

4 years ago

2.5.1-canary.14

4 years ago

2.5.1-canary.13

4 years ago

2.5.1-canary.11

4 years ago

2.5.1-canary.12

4 years ago

2.5.1-canary.8

4 years ago

2.5.1-canary.7

4 years ago

2.5.1-canary.6

4 years ago

2.5.1-canary.5

4 years ago

2.5.1-canary.9

4 years ago

2.5.1-canary.10

4 years ago

2.5.1-canary.4

4 years ago

2.5.1-canary.3

4 years ago

2.5.1-canary.2

4 years ago

2.5.1-canary.1

4 years ago

2.5.1-canary.0

4 years ago

2.5.0

4 years ago

2.4.1-canary.21

4 years ago

2.4.1-canary.22

4 years ago

2.4.1-canary.20

4 years ago

2.4.1-canary.19

4 years ago

2.4.1-canary.17

4 years ago

2.4.1-canary.18

4 years ago

2.4.1-canary.16

4 years ago

2.4.1-canary.15

4 years ago

2.4.1-canary.14

4 years ago

2.4.1-canary.13

4 years ago

2.4.1-canary.9

4 years ago

2.4.1-canary.10

4 years ago

2.4.1-canary.11

4 years ago

2.4.1-canary.12

4 years ago

2.4.1-canary.8

4 years ago

2.4.1-canary.7

4 years ago

2.4.1-canary.6

4 years ago

2.4.1-canary.4

4 years ago

2.4.1-canary.3

4 years ago

2.4.1-canary.2

4 years ago

2.4.1-canary.1

4 years ago

2.4.1-canary.0

4 years ago

2.4.0

4 years ago

2.3.1-canary.3

4 years ago

2.3.1-canary.1

4 years ago

2.3.1-canary.2

4 years ago

2.3.0

4 years ago

2.3.1-canary.0

4 years ago

2.2.1-canary.1

4 years ago

2.2.1-canary.0

4 years ago

2.2.0

4 years ago

2.1.1-canary.2

4 years ago

2.1.1-canary.1

4 years ago

2.1.0

4 years ago

2.0.1-canary.6

4 years ago

2.1.1-canary.0

4 years ago

2.0.1-canary.4

4 years ago

2.0.1-canary.3

4 years ago

2.0.1-canary.0

4 years ago

2.0.0

4 years ago

1.8.2-canary.2

4 years ago

1.8.2-canary.0

4 years ago

1.7.8-canary.2

4 years ago

1.8.1-canary.0

4 years ago

1.7.8-canary.1

4 years ago

1.7.8-canary.0

4 years ago

1.7.7-canary.5

4 years ago

1.7.7-canary.4

4 years ago

1.7.7-canary.3

4 years ago

1.7.7-canary.2

4 years ago

1.7.6-canary.11

4 years ago

1.7.7-canary.0

4 years ago

1.7.6-canary.10

4 years ago

1.7.6-canary.9

4 years ago

1.7.2-canary.0

4 years ago

1.7.2

4 years ago

1.7.1

4 years ago

1.7.1-canary.10

4 years ago

1.7.1-canary.6

4 years ago

1.0.3-canary.3

4 years ago

1.0.3

4 years ago

1.0.2

4 years ago

1.0.2-canary.1

4 years ago

1.0.0

4 years ago

1.0.0-canary.55

4 years ago

1.0.0-canary.23

4 years ago