Vale Server is a desktop application that brings your editorial style guide to life.
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 101
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.
For example, as a writer, you probably have certain guidelines that you need to follow—e.g., naming conventions, word usage, and capitalization styles—that allow the company or organization you’re writing for to maintain a consistent voice across all of its media. Vale Server allows you to automate the process of checking for these stylistic aspects of writing.
Vale Server’s key feature is the notion of styles. Styles are collections of user-created rules that enforce arbitrary guidelines.
Vale Server comes with a growing selection of open-source, pre-made styles for many popular style guides and writing tools (of course, you can also create your own using the extension system).
The biggest styles-related change is the introduction of the Vale Dashboard (shown above). The Vale Dashboard allows you to browse, install, and update any style that has been submitted to the new style library. This is a significant improvement over the find-download-unzip-copy workflow that Vale currently requires.
That said, Vale Server is still 100% compatible with the old StylesPath workflow—meaning you can still use custom styles that you don’t want to submit to the public library.
Vale Server (as discussed in the previous post) introduces a new project-management system. Consider the following scenario:
You’re working for an organization that adheres to the Microsoft Writing Style Guide, so you’ve installed the style and added it to your configuration file.
A few weeks later, a new version of the style is released with a few bug fixes and enhancements. What do you do now? You either have to overwrite your changes altogether or slowly migrate each customized rule individually.
Projects make this process much easier. Each project is a single folder (stored at
<StylesPath>/Vocab/<Project name>/) that consists of two text files—
reject.txt—that contain one word or phrase per line (similar to how ignore files currently work).
All entries in accept.txt are automatically added to a case-insensitive substitution rule (
Vocab.Terms), ensuring that any occurrences of these words or phrases exactly match their corresponding entry in
accept.txt. Each term is automatically added to every exception list in all inherited styles—meaning that you now only need to update your project’s vocabulary to customize third-party styles.
Entries in reject.txt are automatically added to an existence rule (
Vocab.Avoid) that will flag all occurrences as errors.
Additionally, instead of having to add your customizations to the text files themselves, you can manage different project-based *vocabularies *through the dashboard (shown above).
Unlike most writing applications, Vale Server doesn’t include its own editor—its functionality is exposed over a server that communicates with other applications (referred to as “clients”). This allows you to use your preferred tools while still using Vale Server to check your content.
Currently, clients are available for **Sublime Text 3, Atom, Visual Studio Code, and Google Docs** (you can also check content via your clipboard). These clients take full advantage of Vale Server’s integration with the desktop, allowing for better control of and navigation to your Vale-related assets.
Some of the new features you can expect in many of the clients are:
Jump to Rule Definition: Access a rule’s definition from its in-text occurrences.
Jump to Source: Open the relevant section of a style guide from occurrences of its rules.
StylesPath Navigation: Browse and edit your styles from within your editor.
Vale Server includes an embedded HTTP server that runs on localhost, meaning that your content never has to be sent to a remote server.
The benefit to this approach (over the CLI) is that Vale Server has the ability to communicate with applications that run in a sandboxed environment (as is the case with the Google Docs add-on) without losing the ability to access your local configuration details.
Vale vs. Vale Server
I don’t view Vale and Vale Server as competing products: Vale excels in CI/CD environments, while Vale Server offers a better overall experience for individual writers through improved (and expanded) plugins for other apps, a GUI, project management, and a web-based dashboard.
I intend to continue developing Vale and aim to keep a high level of compatibility between the two products.
Ideally, I’d say that you should have:
A precise set of guidelines (i.e., error-level, fail-worthy rules) checked through Vale on your CI service; and
an expanded set of guidelines checked (on-the-fly) through Vale Server’s various client integrations.
Vale Server is currently available for a one-off $40 purchase. This includes all platforms (macOS and Windows for now; Linux is on its way!), clients, and future updates. I also offer support through either email (firstname.lastname@example.org) or GitHub issues (my response times are typically less than 24 hours).
In future updates of Vale Server, you can expect (in no particular order):
Microsoft Word and web browser clients;
an interactive Rule Creator for the dashboard;
multiple new styles (including a grammar-focused one);
support for XML documents; and
the ability to sync your projects across multiple computers and users.
If you’d like to learn more, read the documentation, or purchase a license, please visit the Vale Server website.