Need more than a rule playground? Vale CMS authors full Vale projects: config, rules, vocabularies, tests, and Git-backed changes.
Explore Vale CMSMedia Library
Articles, talks, and videos about Vale from across the community.
Search the full library, including .
Vale checks text against configurable rules, but those rules are regular expressions and carry no sense of context. This talk pairs the Vale MCP server with open models to see how far a rule-based linter and an LLM get together — an open alternative to the proprietary grammar tools.
Chris Chinchilla
An updated tutorial on linting your OpenAPI Specification files, using Views to target the prose fields you care about.
jdkato
A conference workshop on adopting Vale: installation, custom dictionaries, configuring it per format, and adapting a style guide — automation for the technical writer, in the way unit tests and linters support the developer.
Alec Clews
A ruleset that flags the patterns of AI-generated prose, graded by confidence: outright chatbot artifacts, likely tells like hedging clusters and knowledge-cutoff references, and common-but-suspicious habits. Derived from Wikipedia's "Signs of AI writing".
Christian Miles
Learn how we use Vale.sh, a programmatic writing linter, and how we use it at Spectro Cloud.
Karl Cardenas | Spectro Cloud
A guide to configuring Vale as a prose linter in Neovim, from the config file to running vale sync.
Tristan Kreuziger
Manually vs. AI-prompting approach
Diana Cheung
Learn how Datadog’s Documentation team uses a linter to shift quality left.
Datadog
Lint the documentation in your source code repository with Vale. Learn how to by reading this article from the Stream development team.
Jeroen Leenarts | Stream
From design docs to wikis, README files, inline comments in code or even articles like this one, engineers write more prose every day than they realize.
François Violette | Contentsquare
Learn the importance of a style guide in technical writing and how Vale ensures your content complies with it.
MARYAM SULEMANI | Meilisearch
Learn how to setup and use vale, a syntax-aware prose linter with neovim for technical writing be it personal blogs or technical documentation.
Bhupesh Varshney
Guest post originally published on the Chronosphere blog by Chris Ward The discussions on what represents negative, biased, and diverse language continue in many open source communities…
Chris Ward
Vale is a tool that brings code-like linting to text. You can run the tool on a file and it shows validation errors based on designated Style Guides.
Tara English-Sweeney
In a world that is increasingly going remote, prioritizing good documentation and good documentation workflow is important. In this article, you’ll learn how to save hours of tedious work of writing, updating, and correcting technical documentation. In this article, you will learn how to automate your documentation workflow with Vale and GitHub Actions.
Portia Burton
Code linters support developers by catching errors and stylistic issues in code, such as bad formatting or keywords in the wrong places. The term comes from lint traps in dryer machines, which capture the tiny bits of fiber that separate from cloth.
Fabrizio Ferri Benedetti
If you've ever done any sort of continuous long form writing, you'll eventually discover that grammar and spell checking tools break down and become more of a distraction than a benefit.
Thedro Neely
Most of my experience has been working with organizations that heavily invested in DITA infrastructure. During my time with IBM, we used to depend upon Acrolinx checker to be our pseudo-editor. If you have ever used Acrolinx, you know the ease of use it offers. For organizations that invest in the docs-as-code methodology, mostly startups, might find it quite an investment to indulge in Acrolinx, and that too for the TW team (budget for TW team?
Shweta Shetye
Vale Server now works with Gmail, GitHub, Medium, dev.to, WordPress, Confluence, … and more!
jdkato
Making the Buildkite docs more inclusive using automatic tests run on Buildkite 🛠 These linters won't fix your docs for you, but they will tell you where to fix them yourself
Sam Wright, Buildkite
A tutorial on linting your OpenAPI Specification files
jdkato
Sofie would like to introduce you to the new Documentation style guide
Sofie Toft Kristensen, Umbraco
Testing your documentation allows you to make sure it is in a consistent state. Doing this gives your users a better experience, and reduces stress around common issues as a writer. This article by...
Write the Docs
Check out how this developer used human language linter tool Vale to construct tests that check work for not only spelling and grammar, but usage and style, too.
Chris Ward