Personally interested where the confusion is- maybe unfamiliarity with "linting" or "prose"?
Personally interested where the confusion is- maybe unfamiliarity with "linting" or "prose"?
It would also be nice to see examples of what it can do. Again, if it's hard Coded grammar it would be nice to see the complexity it can handle, if llm, the lengths the token limits can manage
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.
Instead of the long list of integrations, more exposition and context would be helpful, or at least an immediate link to an introduction page providing that. In earlier times, software documentation would provide a whole introductory book chapter providing the context, use cases, and some examples.
As a side note, regarding the screenshot, I’m wondering whether the tool also provides a rationale for each item, as the displayed text isn’t very informational on the why.
There is no clear explanation of what it actually is, just a vague sentence saying "brings your editorial style guide to life" which can mean a lot of things. And the screenshot is a wall of text in the smallest font size across the entire page (even smaller than the labels of the logos that make up 50% of the area), so if it was intended as carrier of important information it wasn't the right choice.
The HN post title says more in four words than the entire landing page.