When I launched Vale Server last year, supporting browsers and other web-based applications was one of the primary goals. The initial release included support for Chrome, but there were still a lot of details that needed to be figured out.
The extension has since been completely re-written to better support the features and ideals of Vale Server — specifically, the extension:
Almost exactly two years ago, I announced the v1.0 release of Vale. And a lot has happened since then: I’ve made over 70 individual releases (including a second major version), launched a desktop application, and watched Vale’s community grow dramatically.
Vale has been downloaded over 200,000 times, and is actively helping writers across hundreds of projects — including
Through all of…
The latest development cycle for Vale Server focused almost entirely on in-editor performance with the specific goal of improving the on-the-fly linting experience.
The first change you’ll notice in v1.8 is that the action-processing engine has been completely re-written from Python to Go, incorporating many performance enhancements along the way.
Overall, the re-write allowed Vale Server to see an average decrease in response time of around 80.6%.
In addition to the performance gains, the new action-processing engine is going to see a number of general purpose feature additions in the next few releases — including the ability to manage Vale…
In this post, we’ll take a look at the process of writing new rules for Vale (the command-line tool) and Vale Server (the desktop application). The goal for this post is to supplement the existing documentation by covering possible areas of confusion and potential “gotchas.”
But first, we need to define a few terms that you’ll encounter throughout this post and other documentation:
I’m pleased to announce v1.4 of Vale Server today, the fourth major release of Vale’s desktop application. Development for v1.4 was almost entirely focused on improving the Dashboard, including the new Studio page.
One of Vale’s most popular features is its support for YAML-based rules, which allow for a high degree of customization and extensibility without requiring any programming experience. The new Studio dashboard page leverages the machine-readable nature of these YAML files to offer a suite of validation and debugging tools.
At the most basic level, Vale Studio will warn about “malformed” rules — such as those with YAML…
LanguageTool, Rule Actions, updated clients, and more!
The past few months have been quite busy in terms of Vale and Vale Server development, I’ve released Vale v2.0.0-beta, Vale Server v1.2, and new versions of the Atom, Sublime Text, and Visual Studio Code clients.
Today I’m here to announce yet another new release, Vale Server 1.3, which builds off of a bunch of work that’s been done with Vale v2.0.0 and the new text editor clients.
While Vale Server is primarily concerned with enforcing certain writing styles, the ability to provide grammar-related suggestions has been a popular feature request. v1.3 …
OpenAPI Specification files provide machine-readable (JSON or YAML) descriptions of APIs and often contain snippets of text suitable for linting.
The problem is that the target text can be hard to reach from a linting perspective. For instance, consider the following basic example:
As you can see above, the only parts we’re really interested in are the
description (which can contain Markdown), and
In the following sections, we’ll discuss the three main techniques for linting specification files using Vale (an open-source linter for prose). For the examples, we’ll be referencing the
petstore.yaml file from Swagger.
With Vale rapidly approaching v2.0.0 and the release of the Vale Server desktop app, the amount of possible workflows and use cases is at an all-time high. For the sake of this post, we’ll be focusing on the two basic classes of use cases:
The goal is to cover the basic details of each workflow type and provide some general best practices. However, there’s no…
Almost two months ago, I announced that Vale was coming to the desktop. The goal was simple: move away from the command-line environment, while making it easier to manage Vale-related files and folders.
In this post, I’ll discuss the progress I’ve made and the new features (and enhancements) you can make use of in your writing workflow.
Vale Server is a cross-platform (currently available for macOS and Windows; Linux is on its way) desktop application that helps you “codify” editorial guidelines.
8 months ago, I released the first stable version of Vale. Since then, I’ve shifted my focus to bringing Vale’s command-line functionality to a native desktop application. This post will discuss some of the enhancements and refinements that have been implemented along the way.
Vale Server maintains Vale’s high standards for performance and privacy. It consists of three components: