Skip to content

build a process for checking jargon  #213

Open

Description

@kkowalsky

Mapbox has a nice tool for de-jargon-ifying that could be implemented to make sure the writing style guide is being enforced

Activity

  1. self-assigned this
    on Oct 17, 2016
  2. rmglennon commented on Oct 17, 2016

    @rmglennon
    Member

    would love this.

    See also research about other checking: #20

  3. migurski commented on Oct 17, 2016

    @migurski
    Contributor

    If we use something like this and keep our current decentralized docs process, we’re going to want to change the build process to make it less likely that a non-compliant docs source does not hold up an entire release.

  4. kkowalsky commented on Nov 2, 2016

    @kkowalsky
    MemberAuthor

    words to add:

    • company/organization names (OpenStreetMap for example)
    • software names (GitHub, Leaflet, etc.)
    • common terms (open-source vs. open source)

    feel free to edit this comment to add more words to look out for!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions