markdownlint
vale
Our great sponsors
markdownlint | vale | |
---|---|---|
7 | 46 | |
4,389 | 4,119 | |
- | 3.7% | |
9.6 | 9.3 | |
4 days ago | 11 days ago | |
JavaScript | Go | |
MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
markdownlint
-
Recommended Linters
markdownlint - A Node.js style checker and lint tool for Markdown/CommonMark files.
-
Regal v0.14.0 released
Improvements - The prefer-some-in-iteration rule will by default no longer flag iteration where a sub-attribute is used, like input[_].item - The use-in-operator rule has been extended to include more types of items, leading to better discovery of locations where in should be used - Remove replace directive in go.mod that made hard to integrate Regal as a library - The project now uses markdownlint to ensure consistent formatting of its documentation - The Go API now allows reading custom rules from an fs.FS filesystem
-
Project idea: port markdownlint to Rust
People are always looking for simple projects to learn Rust with, so here's one for anyone who's currently looking. Port markdownlint to Rust. Markdownlint is ~3.3k lines of JavaScript (including the lint implementation themselves!), so I reckon it's pretty doable.
-
VS Code - Catch errors in your markdown files
The markdownlint VS Code extension is powered by the Node library of the same name. Its usage is quite similar to ESLint. It has a set of rules that can be configured, errors are highlighted, and you can automatically fix simple errors.
-
Markdown Linting
Markdown Lint
-
10 Best Visual Studio Code Extensions for Flutter Development
There are no compilers in the Flutter project that guarantee to find issues in README.md or CHANGELOG.md files. To remedy this, the Markdownlint plugin provides a set of guidelines to encourage Markdown file standards and uniformity. You can use this extension to check for problems locally and verify the content before publishing it live. Browse the user manual to learn more about rules.
vale
- Software Technical Writing: A Guidebook [pdf]
- Grammarly editor writing service are malfunctioning
- Vale.sh – A Linter for Prose
- Val, a high-level systems programming language
-
Just Simply – Stop saying how simple things are in our docs
> Write in US English with US grammar. (Tested in British.yml.)
heh, that was funny but it turns out the file is a list of British words checked using Vale, which I just learned existed: https://github.com/errata-ai/vale#readme (MIT)
Also, another TIL is that the "e" version of gray is British https://gitlab.com/gitlab-org/gitlab/-/blob/master/doc/.vale... I had previously erroneously assumed they were just one of those quirks of English (which, I guess is still true but it is less random than I thought)
-
What terminal apps are you using?
vale to spell check and enforce writing style on my articles
-
6 ways we improved our documentation in 2022
Similar to how a software has integration or unit tests that are built to make sure changes in the software don’t break the entire system, we implemented tests for our documentation’s style guide using Vale and ESLint.
-
A simple guide on words to avoid in UK government
Related: Vale is a plain-language or "prose" linter. Built a version of this for use with the US DVA
-
How could I use neovim for general writing and annotations?
For longer writing, I like using vale.
-
nvim-tundra v0.2.0 - A punchy, dark theme for Neovim!
Hi r/Neovim! Today I released v0.2.0 for the [Tundra](https://github.com/sam4llis/nvim-tundra) theme so thought I’d post it here in case anybody is interested. ## Highlights: - Added `dim_inactive_windows` table in the Tundra `setup` function - when enabled, non-current windows will inherit the background colour `dim_inactive_windows.color`. - Added `:Tundra` command line sugar. This allows users to change configuration settings in real-time instead of having to reload their configuration. - `:Tundra toggle_transparency` - toggles `transparent_background` flag. - `:Tundra toggle_dim` - toggles `dim_inactive_windows.enabled` flag. - [nvim-treesitter](https://github.com/nvim-treesitter/nvim-treesitter) integration now requires Neovim 0.8. Obsolete `TS*` highlight groups were removed from nvim-treesitter and Tundra will no longer support older highlight groups. To use the obsolete highlight groups, downgrade to Tundra v0.1.0. See [this](https://github.com/nvim-treesitter/nvim-treesitter/pull/3656) for more information. - Support for common terminals and software including Alacritty, fzf, iTerm-2, WezTerm, and Windows Terminal. - Improvement of Tundra documentation. - Rewritten using [Vale](https://vale.sh) to keep a consistent style guide. You can find more information about the Tundra theme over at its [GitHub repository](https://github.com/sam4llis/nvim-tundra). Thanks for reading!
What are some alternatives?
lsp-grammarly - lsp-mode ❤️ grammarly
proselint - A linter for prose.
nvim-lspconfig - Quickstart configs for Nvim LSP
write-good - Naive linter for English prose
markdownlint - Repository for the markdownlint-mdl-action Github Action
remark-lint - plugins to check (lint) markdown code style
markdownlint - Markdown lint tool
languagetool - Style and Grammar Checker for 25+ Languages
flycheck-grammarly - Grammarly support for Flycheck
packages - :package: A collection of pre-packaged, Vale-compatible style guides and configurations.