Skip to content
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

Enhance Plone documentation style guide #1864

Merged
merged 2 commits into from
Feb 16, 2025

Conversation

stevepiercy
Copy link
Contributor

@stevepiercy stevepiercy commented Feb 16, 2025

  • Clarify why we use one sentence per line
  • Add links to Microsoft Style Guide for verb tense, usage, and examples.
  • Add .vscode/settings.json reference and example file.

📚 Documentation preview 📚: https://plone6--1864.org.readthedocs.build/

- Clarify why we use one sentence per line
- Add links to Microsoft Style Guide for verb tense, usage, and examples.
- Add `.vscode/settings.json` reference and example file.
Copy link
Member

@gforcada gforcada left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Although I'm a huge fan of semantic line breaks, and that you can submit suggestions for multiple lines (see docs), the other changes look good 👍🏾

@stevepiercy stevepiercy merged commit 765cbee into 6.0 Feb 16, 2025
3 checks passed
@stevepiercy stevepiercy deleted the docs-style-guide-clarifications branch February 16, 2025 22:27
@stevepiercy
Copy link
Contributor Author

In addition to the reasons against semantic line breaks already stated in this PR, they are a barrier to contributors who are not fluent in English. How would you teach it to volunteer contributors without scaring them away?

So between that, PEP8, and avoiding horizontal scrolling during diff reviews, the one sentence per line pattern is a reasonable compromise for our international audience.

Thanks for the link for the multiple line suggestion. TIL. I'll amend the docs. It would be good to point people to that. Almost all of the suggestions I see are single-line.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Done
Development

Successfully merging this pull request may close these issues.

3 participants