-
-
Notifications
You must be signed in to change notification settings - Fork 168
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Consider using Vale for spellcheck and style guide #1347
Comments
I like your suggestion to use Vale.
Vale can help me writing better style like the both examples above illustrate. Apart from a tool for obeying style guides, I have a spell checker extension enabled in VSCode: "Code Spell Checker" from "Street Side Software" which is awesome. |
Thanks for the feedback. I also want to try it out before we decide which styles to adopt. Is the passive voice or first-person plural OK to use in some contexts? Trainings has a different context than Documentation, so perhaps "We" is OK in Trainings because we are working together and in person. For VSCode, I think we should mention that extension in our contributing docs. PyCharm has a built-in spellchecker. Vale integrates with both, so we can add specific words to include or exclude in our spellcheck dictionaries. Let's keep experimenting and get more feedback from authors. I think it is OK to suggest tools now so that authors can try them and so we can collect feedback from their use. |
@ksuess @polyester do you have a preference for Vale configuration? I have no preference. |
I have preference for Microsoft style guide - several reasons, but overall it's an easier one to work with /explain to non-native speakers and more attention to non-tech audiences. |
I've added the following styles to my Vale. Should I add or remove any? For calling vale via make, I am currently listing all the directories with glob syntax, but it is not very clever. vale docs/*.md \
docs/backend/*.md \
docs/backend/upgrading/*.md \
docs/backend/upgrading/version-specific-migration/*.md
# and so on Is there a clever glob argument? |
Aha! vale docs/**/*.md |
I find the 'readability' warnings to be less than useful, they're all "try to keep the GobblediGook (x.y) Index below (z). Usually meaning your text is a bit convoluted, but not being specific. Line-by-line warnings are more useful, and are included in the others. I would start with a small set, can always be added/changed later |
I've compared the base options on two chapters of my training. I will use and enhance my training documentation with spell checking enabled in VSCode. Plugins
The lexicon Go for it! |
my
|
Please share this file! |
For testing purpose I added just some words to
|
Getting closer. Here's the StylesPath = styles
MinAlertLevel = suggestion
Vocab = Base,Plone
Packages = Microsoft
[*]
BasedOnStyles = Vale, Microsoft And I started
Vale cannot find the directories in submodules, or maybe ignores them via vale --no-wrap docs/**/*.md \
docs/volto/**/*.md \
docs/plone.api/**/*.md \
docs/plone.restapi/**/*.md
✖ 1865 errors, 848 warnings and 2968 suggestions in 254 files. |
And on training: |
See discussion of RichText vs. rich text usage: plone/plone.volto#106 (review) |
Closed by #1366 |
Plone Documentation versions affected
Description
Our current spellchecker is not well supported. For example, it will mark "add-on" as an incorrectly spelled word because it does not support hyphenation among other shortcomings. It also cannot be installed on M1 (and maybe M2) based macs.
@polyester suggested Vale as a replacement. I read its docs, and I am thoroughly impressed by its defaults, extensibility, and integration with editors and GitHub Actions as a Docker image.
If others agree, then I would implement it as a guide only to provide feedback to correct common misspellings and style errors, and suggest corrections. I would suggest that authors optionally run Vale after they have completed their first draft, allowing them to both "stay in the zone" and improve their writing quality.
The text was updated successfully, but these errors were encountered: