Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
G
gitlab-ce
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
0
Merge Requests
0
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
Léo-Paul Géneau
gitlab-ce
Commits
1cfe83ea
Commit
1cfe83ea
authored
Mar 14, 2019
by
Evan Read
Committed by
Marcia Ramos
Mar 14, 2019
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Change line length recommendation
parent
516987e4
Changes
1
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
3 additions
and
4 deletions
+3
-4
doc/development/documentation/styleguide.md
doc/development/documentation/styleguide.md
+3
-4
No files found.
doc/development/documentation/styleguide.md
View file @
1cfe83ea
...
...
@@ -80,11 +80,10 @@ yield a useful result, and ensuring content is helpful and easy to consume.
## Text
-
Split up long lines (wrap text), this makes it much easier to review and edit. Only
double line breaks are shown as a full line break by creating new paragraphs.
80-100 characters is the recommended line length.
-
Splitting long lines (preferably up to 100 characters) can make it easier to provide feedback on small chunks of text.
-
Insert an empty line for new paragraphs.
-
Use sentence case for titles, headings, labels, menu items, and buttons.
-
Jump a
line between different markups (e.g., after every paragraph, header, list, etc). Example:
-
Insert an empty
line between different markups (e.g., after every paragraph, header, list, etc). Example:
```md
## Header
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment