You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I just went through some PRs and realized we should agree to some conventions to make sure the we use a consistent style.
Here are some examples where we currently have inconsistencies. Feel free to edit this post to add things you find when reading.
Headlines
There are cases of capitalization in headlines, e.g. Import Options or Cityjson-Specific Import Options.
I suggest we use regular english spelling and do not capitalize things.
Spelling
There are inconsistencies in spellings of some names.
This is the correct spelling:
CityGML
CityJSON
citydb-tool
File paths
File paths and file names should be styled as code. There are some cases where this is not the case.
Code blocks
I found several codeblocks I found hard to read, because they exceeded the width of the block/page. For instance:
I suggest we limit the width of codeblocks to a length that does not require scrolling. This can be done using line continuation. Check out the Docker pages for examples for windows and linux.
Important
Line continuation can be tricky! Make sure to test if the new command can be executed when it's copied from the code box in the rendered docs!
I used this style to provide code boxes for windows and linux:
Hey all,
@clausnagel @yaozhihang @SchultzeMax @marina-rug @MScMOSS @thomashkolbe
I just went through some PRs and realized we should agree to some conventions to make sure the we use a consistent style.
Here are some examples where we currently have inconsistencies. Feel free to edit this post to add things you find when reading.
Headlines
There are cases of capitalization in headlines, e.g.
Import Options
orCityjson-Specific Import Options
.I suggest we use regular english spelling and do not capitalize things.
Spelling
There are inconsistencies in spellings of some names.
This is the correct spelling:
File paths
File paths and file names should be styled as
code
. There are some cases where this is not the case.Code blocks
I found several codeblocks I found hard to read, because they exceeded the width of the block/page. For instance:
I suggest we limit the width of codeblocks to a length that does not require scrolling. This can be done using line continuation. Check out the Docker pages for examples for windows and linux.
Important
Line continuation can be tricky! Make sure to test if the new command can be executed when it's copied from the code box in the rendered docs!
I used this style to provide code boxes for windows and linux:
This will render like this:
Is everybody OK with the conventions I outlined above? Is something missing? Please comment if you would like to have it differently.
The text was updated successfully, but these errors were encountered: