31–40 of 89 posts
I wrote a blogpost how I use Vale and how you can do it too - https://vinckr.com/blog/open-source-stylecheck/
Links are unreadable in that blog post on iOS/Safari.
tags is #302b5f, a very dark desaturated blue and the font color is #262626, very dark gray (mostly black)My favorite is a tool called write-good https://github.com/btford/write-good
As there's a theme in comments here - I'm surprised people are so confused by the landing page. Between "a linter for prose" and the screenshot at the top of the page, I found it quite clear what the use case and point of the tool was. Personally interested where the confusion is- maybe unfamiliarity with "linting" or "prose"?
1. "Your style, our editor" Wait is this an editor or a command line tool? I was able to figure it out but the word "editor" is ambiguous here.
2. "that brings your editorial style guide to life." Ok, so do I have to write all my own rules? Or is it like eslint where I choose a base config with ability to override, and possibly add more? These questions are so fundamental I would like to see succint answers at least hinted at in another tag line or short paragraph, even if I can figure them out by digging into the docs.
As there's a theme in comments here - I'm surprised people are so confused by the landing page. Between "a linter for prose" and the screenshot at the top of the page, I found it quite clear what the use case and point of the tool was. Personally interested where the confusion is- maybe unfamiliarity with "linting" or "prose"?
I don't really understand this, what is a linter for prose? Like Grammarly? Is it an end-user product or for a programmatic interface? If the former, why are there "integrations?" What does it mean to integrate this into Kong, for example? Does it work through VSCode? Edit: Ok, now I see, it is like an offline version of Grammarly for the editor of your choosing, as well as a lint tool for CI for your docs, like docs…
But what is it? Is this like Grammarly? Maybe LanguageTool? I paged through most of the docs and I’m still not entirely sure what this does or why I might want to use it.
Have tried to use this a few times but it's a big lift. Like adding unit tests to an existing application, it's a good idea to start small. And vale doesn't make this super easy (at least I couldn't figure out an easy way to do this). If I could wave my wand, I'd want a way to: * apply vale to just the doc I was working on * have a minimal set of rules * add to them over time At $curjob, we have a detailed public lis…
I think it's probably because the purpose of computer languages is different from human language. It's certainly valuable to have a linter to make sure the code works, and there's probably value in "style" as well for readability.
But when you get to human language, I don't know, feels like you have the potential to suck out soul/creativity etc. As in, I imagine you throw a great poem or something in here and of course it will tear it apart.
I'm trying to figure out why I instinctively hate this. I think it's probably because the purpose of computer languages is different from human language. It's certainly valuable to have a linter to make sure the code works, and there's probably value in "style" as well for readability. But when you get to human language, I don't know, feels like you have the potential to suck out soul/creativity etc. As in, I imagine…