This repository includes configuration files to ensure consistent formatting across different editors and IDEs used by documentation writers.
Ensure the following steps are taken and configurations are in place before making substantial docs changes.
If you're using Visual Studio Code, the settings in .vscode/settings.json should be automatically applied when you open this project. No additional setup required.
Most modern IDEs support EditorConfig. The .editorconfig file in the root directory will automatically configure:
- IntelliJ IDEA / PyCharm / WebStorm
- Sublime Text
- Atom
- Vim
- Emacs
- And many others
- 1 tab = 4 spaces for all files except:
- JSON files: 2 spaces
- YAML files: 2 spaces
- CSS/HTML files: 2 spaces
- No hard line breaks for markdown files
- Word wrap is enabled but doesn't insert hard breaks
- Long lines are visually wrapped but remain as single lines in the file
- Unix-style line endings (
\n) for all files - Trailing whitespace is automatically trimmed
- Final newline is automatically inserted
- Preserve trailing spaces in markdown (needed for line breaks)
- No automatic formatting on save
- Word wrap enabled for readability
- No ruler/column guides
If your IDE doesn't automatically pick up these settings, configure manually:
Tab Size: 4 spaces
Insert Spaces: Yes (not tabs)
Word Wrap: On
Auto Format on Save: Off
Trim Trailing Whitespace: Yes
Insert Final Newline: Yes
Word Wrap: On
Hard Line Breaks: Off
Preserve Trailing Spaces: Yes
Max Line Length: Unlimited
Python: 4 spaces
JavaScript/TypeScript: 4 spaces
JSON: 2 spaces
YAML: 2 spaces
For the best writing experience in VSCode, consider installing:
- EditorConfig for VS Code - Automatically applies .editorconfig settings
- markdownlint - Markdown editing enhancements
- Markdown All in One - Markdown editing enhancements
- MDX - Syntax highlighting for
.mdxfiles - Prettier - Code formatter (disabled for markdown in our settings)
- Allows flexibility in how content is displayed across different devices
- Prevents awkward line breaks when content is edited
- Better for collaborative editing and version control
- Responsive to different screen sizes
- Consistent with Python conventions (used in code examples)
- Good readability for nested content
- Standard across most programming languages
- Prevents unwanted changes to carefully crafted markdown
- Avoids breaking custom formatting like tables or code blocks
- Gives writers full control over content structure
- Restart VSCode after opening the project
- Check that you're in the docs folder (not a parent directory)
- Verify
.vscode/settings.jsonexists in the project root
- Ensure your IDE supports EditorConfig
- Install the EditorConfig plugin if needed
- Check that
.editorconfigis in the project root - Restart your IDE
If automatic configuration isn't working, manually configure your IDE using the settings listed above.