Skip to content

Commit 1a15b6c

Browse files
Improve markdown linting (openhab#1906)
* Improve markdownlint configuration. Signed-off-by: Jerome Luckenbach <[email protected]> * Apply changes to current linting rules. Signed-off-by: Jerome Luckenbach <[email protected]> Signed-off-by: Jerome Luckenbach <[email protected]>
1 parent b0a3de9 commit 1a15b6c

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

59 files changed

+366
-410
lines changed

.github/.markdownlint.yaml

+4
Original file line numberDiff line numberDiff line change
@@ -25,3 +25,7 @@ MD033: false
2525
# Code block style
2626
MD046:
2727
style: fenced
28+
29+
#Emphasiszis in asterisk
30+
MD049:
31+
style: underscore

.markdownlint.yaml

+6
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,6 @@
1+
# Reference workflow file in ".github folder"
2+
# to allow local development and workflow with one configuration
3+
4+
extends: "./.github/.markdownlint.yaml"
5+
6+
# Any configuration should be done in the workflow file

README.md

+8-8
Original file line numberDiff line numberDiff line change
@@ -8,9 +8,9 @@ The result is available at [https://openhab.org/docs/](https://www.openhab.org/d
88

99
## How it works
1010

11-
In this repo you can find and improve all *general* documentation contents.
11+
In this repo you can find and improve all _general_ documentation contents.
1212
In fact that is all you can see in the `main` branch.
13-
There are also other *read-only* branches, which hold external content like the *add-ons* and *concepts* documentation.
13+
There are also other _read-only_ branches, which hold external content like the _add-ons_ and _concepts_ documentation.
1414
We will read about them later.
1515

1616
### So I can't improve an add-on article here?
@@ -44,7 +44,7 @@ You can read a bit more below about our external resources and how we get them.
4444

4545
### Automatically Generated Parts
4646

47-
Those parts include __all__ add-on documentation files, no matter if they are from the `openhab-core` repo, the `openhab-addons` repo or any special binding repo like *habmin*, *zwave* or the *alexa skill*.
47+
Those parts include __all__ add-on documentation files, no matter if they are from the `openhab-core` repo, the `openhab-addons` repo or any special binding repo like _habmin_, _zwave_ or the _alexa skill_.
4848

4949
We are keeping all those files at their original location, because it simply doesn't make sense to keep them here.
5050
Imagine you want to do an improvement of the zwave binding and have to update the readme file in a completely different place.
@@ -60,8 +60,8 @@ The process below is subject to changes until the openHAB 3.x website become the
6060
### How the documentation build works
6161

6262
We have set up our [build server](https://ci.openhab.org/view/Documentation%20(3.x)/) to do the magic automatically.
63-
There are several triggers (mostly time based), which will then *gather the external contents* and move them to our [final](https://github.com/openhab/openhab-docs/tree/final) branch.
64-
You can find this migrated external content in the *final* branch under:
63+
There are several triggers (mostly time based), which will then _gather the external contents_ and move them to our [final](https://github.com/openhab/openhab-docs/tree/final) branch.
64+
You can find this migrated external content in the _final_ branch under:
6565

6666
- `_addons_*`
6767
- `concepts`
@@ -71,14 +71,14 @@ The external content is updated by the following toolchain:
7171

7272
- `update-external-resources.sh``pom.xml``process_addons.groovy`
7373

74-
Everything that gets updated in the *master* branch will be also merged over to the *final* branch automatically.
75-
Afterwards we will redeploy the website with the latest content from the *final* branch at regular intervals.
74+
Everything that gets updated in the _master_ branch will be also merged over to the _final_ branch automatically.
75+
Afterwards we will redeploy the website with the latest content from the _final_ branch at regular intervals.
7676

7777
#### Build triggers investigated
7878

7979
There are two triggers available currently.
8080
The `merge docs` job is triggerd after something has been added to the documentation through this repository.
81-
The `gather external docs` job is started with a **succesful** build of the openhab-distribution.
81+
The `gather external docs` job is started with a __succesful__ build of the openhab-distribution.
8282
A succesful disribution build will include all of the latest changes that have been made to external sources like addons.
8383
So when a distribution build is succesful, we will trigger the gathering of all external sources.
8484

addons/actions.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -177,7 +177,7 @@ The Timer object supports the following methods:
177177

178178
- `cancel`: prevents the scheduled timer from executing. Most of the time `cancel` is used used in conjunction with setting the timer handler to `null` as a convenient indicator that some previously defined timer is now finished with. However setting the handler to `null` does not interact with the timer itself.
179179
- `isActive`: returns `true` if the timer will be executed as scheduled, i.e. it has not been cancelled or completed.
180-
- `isCancelled`: returns `true` if the timer has been cancelled *before* it completed.
180+
- `isCancelled`: returns `true` if the timer has been cancelled _before_ it completed.
181181
- `isRunning`: returns `true` if the code is currently executing (i.e. the timer activated the code but it is not done running).
182182
- `hasTerminated`: returns `true` if the timer has been cancelled or the code has run and completed.
183183
- `reschedule(AbstractInstant instant)`: reschedules the timer to execute at the new time. If the Timer has terminated this method does nothing.
@@ -227,7 +227,7 @@ Notification actions may be placed in Rules to send alerts to mobile devices reg
227227
Three different actions are available:
228228

229229
- `sendNotification(emailAddress, message)`: Sends a notification to a specific cloud instance user
230-
- `sendBroadcastNotification(message)`: Sends a notification to *all* devices of *all* users
230+
- `sendBroadcastNotification(message)`: Sends a notification to _all_ devices of _all_ users
231231
- `sendLogNotification(message)`: Sends a log notification to the `notifications` list at your openHAB Cloud instance. Notifications are NOT sent to any registered devices
232232

233233
For each of the three actions, there's another variant accepting an icon name and a severity:

addons/io.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ title: System Integrations
77

88
openHAB supports services that enable integration with various technologies that don't fall into other add-on categories.
99

10-
Most of the systems mentioned below are integrated via a *Misc* add-on, installed e.g. through UI.
10+
Most of the systems mentioned below are integrated via a _Misc_ add-on, installed e.g. through UI.
1111
Detailed instructions and requirements may be found in the corresponding documentation pages.
1212

1313
<!-- selection not needed for now table id="ios-select" class="striped">

administration/bundles.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -68,7 +68,7 @@ where
6868

6969
These bundle names are used in many places in openHAB, such as in various configuration files.
7070
Logging also makes extensive use of this **package namespace**.
71-
You can see these names listed as the *Symbolic names* of bundles by using the ```-s``` option of _bundle:list_:
71+
You can see these names listed as the _Symbolic names_ of bundles by using the ```-s``` option of _bundle:list_:
7272

7373
```text
7474
openhab> bundle:list -s

administration/console.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -94,7 +94,7 @@ openhab> help bundle:stop
9494

9595
The console also supports auto-completion during input.
9696
Auto-completion proposes possible commands based on the current input and is triggered by a &lt;TAB&gt; press on your keyboard.
97-
So for example entering "*bund*" and pressing the &lt;TAB&gt; key will first extend to the only viable candidate "bundle", a subsequent &lt;TAB&gt; press will result in:
97+
So for example entering "_bund_" and pressing the &lt;TAB&gt; key will first extend to the only viable candidate "bundle", a subsequent &lt;TAB&gt; press will result in:
9898

9999
```text
100100
openhab> bundle

concepts/audio.md

+10-10
Original file line numberDiff line numberDiff line change
@@ -8,31 +8,31 @@ title: Audio & Voice
88
Audio and voice features are an important aspect of any smart home solution as it is a very natural way to interact with the user.
99

1010
openHAB has a very modular architecture that enables many different use cases.
11-
At its core, there is the notion of an *audio stream*.
12-
Audio streams are provided by *audio sources* and consumed by *audio sinks*.
11+
At its core, there is the notion of an _audio stream_.
12+
Audio streams are provided by _audio sources_ and consumed by _audio sinks_.
1313

1414
![audio](images/audio.png)
1515

16-
- *Audio Streams* are essentially byte streams with a given *audio format*.
16+
- _Audio Streams_ are essentially byte streams with a given _audio format_.
1717
They do not need to be limited in size, i.e. it is allowed to have continuous streams, e.g. the input from a microphone or from an Internet radio station.
18-
- *Audio Formats* define the container (e.g. WAV), encoding, bit rate, sample frequency and depth and the bit order (little or big endian).
19-
- *Audio Sources* are services that are capable of producing audio streams.
18+
- _Audio Formats_ define the container (e.g. WAV), encoding, bit rate, sample frequency and depth and the bit order (little or big endian).
19+
- _Audio Sources_ are services that are capable of producing audio streams.
2020
They can support different formats and provide a stream in a requested format upon request.
2121
Typical audio source services are microphones. Typically, a continuous stream is expected from them.
22-
- *Audio Sinks* are services that accept audio streams of certain formats.
22+
- _Audio Sinks_ are services that accept audio streams of certain formats.
2323
Typically, these are expected to play the audio stream, i.e. they are some kind of speaker or media device.
24-
- *Text-to-Speech* (TTS) services are similar to audio sources with respect to the ability to create audio streams.
24+
- _Text-to-Speech_ (TTS) services are similar to audio sources with respect to the ability to create audio streams.
2525
The difference is that they take a string as an input and will synthesize this string to a spoken text using a given voice.
2626
TTS services can provide information about the voices that they support and the locale that those voices are associated with.
2727
Each voice supports exactly one locale.
28-
- *Speech-to-Text* (STT) services are similar to audio sinks, but they do not simply play back the stream, but convert it to a plain string.
28+
- _Speech-to-Text_ (STT) services are similar to audio sinks, but they do not simply play back the stream, but convert it to a plain string.
2929
They provide information about supported formats and locales.
3030

31-
As plain text from an STT service is often not very useful, there is additionally the concept of a *human language interpreter*:
31+
As plain text from an STT service is often not very useful, there is additionally the concept of a _human language interpreter_:
3232

3333
![hli](images/hli.png)
3434

35-
A *Human Language Interpreter* takes a string as an input.
35+
A _Human Language Interpreter_ takes a string as an input.
3636
It then derives actions from it (like sending commands to devices) and/or replies with a string, which opens the possibility to realize conversations.
3737
As such an interpreter is not directly linked to audio streams, but operates on strings only, this can be the basis for any kind of assistant, e.g. for chat bots using the console, XMPP, Twitter or other messaging services.
3838

configuration/addons.md

+3-3
Original file line numberDiff line numberDiff line change
@@ -37,7 +37,7 @@ openhab-binding-network | 3.0.0.M5 | | Uninst
3737
...
3838
```
3939

40-
According to the [naming convention for bundles](/docs/administration/bundles.html#naming-convention-for-bundles) the *id* for the shown example is *network*.
40+
According to the [naming convention for bundles](/docs/administration/bundles.html#naming-convention-for-bundles) the _id_ for the shown example is _network_.
4141

4242
Another way to find the correct `id` is to look at the URL of the add-on documentation page.
4343
For example the url for the [Network Binding documentation](/addons/bindings/network/) is
@@ -48,7 +48,7 @@ https://www.openhab.org/addons/bindings/network/
4848

4949
In this case, the `id` would be "network".
5050

51-
With this information we can now edit the *addons.cfg* file in the `$OPENHAB_CONF/services` folder on the machine you are running openHAB on.
51+
With this information we can now edit the _addons.cfg_ file in the `$OPENHAB_CONF/services` folder on the machine you are running openHAB on.
5252
The path depends on your installation.
5353
You can find out the correct locations on the corresponding documentation pages, e.g. [Linux](/docs/installation/linux.html#file-locations) or [Windows](/docs/installation/windows.html#file-locations).
5454

@@ -62,7 +62,7 @@ transformation = jsonpath
6262
persistence = influxdb
6363
```
6464

65-
To install the network Binding like we want in this example, we just need to add the id *network* to the Binding section.
65+
To install the network Binding like we want in this example, we just need to add the id _network_ to the Binding section.
6666

6767
```text
6868
binding = astro,network

configuration/blockly/index.md

+7-7
Original file line numberDiff line numberDiff line change
@@ -24,12 +24,12 @@ Therefore openHAB also provides a graphical way of writing rules which allows to
2424
The basic idea behind the visual paradigm and representation within openHAB is based on the [Google Blockly Support](https://developers.google.com/blockly) which has been integrated and which provides the basic blocks for programming like the ones on the left and the right side of the below images
2525

2626
{: #blockly-toolbox}
27-
*Blockly toolbox*
27+
_Blockly toolbox_
2828

2929
![blockly-toolbox-1](../images/blockly/blockly-toolbox-1.png)![blockly-toolbox-2](../images/blockly/blockly-toolbox-2.png)![blockly-toolbox-3](../images/blockly/blockly-toolbox-3.png)
3030

3131
All of these provide general functionality that is not specific to openHAB itself. If you want to learn more about how to use them, search for the many blockly tutorials that are available.
32-
However, to leverage the full capabilities more than *50 specific blocks* have been provided that are tailored for easy access of openHAB's capabilities.
32+
However, to leverage the full capabilities more than _50 specific blocks_ have been provided that are tailored for easy access of openHAB's capabilities.
3333

3434
This section provides a detailed description of the specific blocks and provides examples on how to use them. Note that some of the blocks (like voice, streaming or notifications) need some special setup within openHAB - in these case links to the respective documentation is provided.
3535
Also see this ![youtube](../images/blockly/youtube-logo-small.png) [Intro](https://youtu.be/EdllUlJ7p6k?t=295) Quick Intro Blockly Rules
@@ -45,7 +45,7 @@ There is also a help-button available in each section that links to the document
4545

4646
![main-help-button](../images/blockly/blockly-main-help.png)
4747

48-
Please read this information first before asking questions in the forum. *In case you ask for help please always post the respective code that is being generated.*
48+
Please read this information first before asking questions in the forum. _In case you ask for help please always post the respective code that is being generated._
4949

5050
Also there is a good intro about that topic can be viewed at ![youtube](../images/blockly/youtube-logo-small.png) [Various Help Documentation available in openHAB Blocky](https://youtu.be/EdllUlJ7p6k?t=1589)
5151

@@ -111,7 +111,7 @@ Also view ![youtube](../images/blockly/youtube-logo-small.png) [Overview of the
111111

112112
### Items and Things
113113

114-
*Items* and *Things* are the [major entities of openHAB](https://www.openhab.org/docs/concepts/) to control and monitor the home.
114+
_Items_ and _Things_ are the [major entities of openHAB](https://www.openhab.org/docs/concepts/) to control and monitor the home.
115115

116116
[![Items and Things](../images/blockly/blockly-items-and-things-small.png "Items and Things")
117117
](rules-blockly-items-things.html)
@@ -131,7 +131,7 @@ See [Timers and Delays](rules-blockly-timers-and-delays.html) section.
131131
### Date Handling
132132

133133
Date blocks are used as input parameters for other blocks.
134-
Some of these blocks are used by ephemeris blocks, whilst others are used in the persistence section. Therefore blocks are *typed* to assure correct connection to other blocks.
134+
Some of these blocks are used by ephemeris blocks, whilst others are used in the persistence section. Therefore blocks are _typed_ to assure correct connection to other blocks.
135135

136136
[![Date Handling](../images/blockly/blockly-date-handling1-small.png "Dates part 1")
137137
](rules-blockly-date-handling.html) [![Date Handling](../images/blockly/blockly-date-handling2-small.png "Dates Part 2")
@@ -151,7 +151,7 @@ See [Ephemeris](rules-blockly-ephemeris.html) section.
151151

152152
### Voice and Multimedia
153153

154-
This section deals with *playing or streaming audio* to an audio sink e.g a speaker or *saying a text* via using any Text-to-Speech API (e.g. Google's API)
154+
This section deals with _playing or streaming audio_ to an audio sink e.g a speaker or _saying a text_ via using any Text-to-Speech API (e.g. Google's API)
155155

156156
[![Voice and Multimedia](../images/blockly/blockly-voice-and-multimedia-small.png "Voice and Multimedia")
157157
](rules-blockly-voice-and-multimedia.html)
@@ -179,7 +179,7 @@ See [Persistence](rules-blockly-persistence.html) section.
179179

180180
### Value Storage
181181

182-
These blocks enable storing information *for a rule* that is kept after the rule has run, so it can be reused when the rule is run again later in stateful way.
182+
These blocks enable storing information _for a rule_ that is kept after the rule has run, so it can be reused when the rule is run again later in stateful way.
183183

184184
[![Value Storage](../images/blockly/blockly-value-storage-small.png "Value Storage")
185185
](rules-blockly-value-storage.html)

configuration/blockly/rules-blockly-before-using.md

+6-6
Original file line numberDiff line numberDiff line change
@@ -25,17 +25,17 @@ Please read them carefully before asking questions in the forum.
2525
## **OpenHAB Configuration Files**
2626

2727
Some openHAB blocks rely on particular configuration files found in the openHAB configuration folder.
28-
This folder is referred to as $OPENHAB_CONF in this page, and the location of this folder for your setup can be found via the UI: *Help & About* -> *Technical Information* -> *Configuration folder*.
28+
This folder is referred to as $OPENHAB_CONF in this page, and the location of this folder for your setup can be found via the UI: _Help & About_ -> _Technical Information_ -> _Configuration folder_.
2929

3030
- via mounting the files shares from the server to your client-PC.
31-
In the main UI as an admin you can go to *Help & About* and will have the different folder locations under *Technical information*.
31+
In the main UI as an admin you can go to _Help & About_ and will have the different folder locations under _Technical information_.
3232
- the exact configuration of the shares can be found on your server at [/etc/samba/smb.conf](https://github.com/openhab/openhabian/blob/main/includes/smb.conf).
33-
- Use the share *openHAB*-conf when mounting it from Windows or MacOS
33+
- Use the share _openHAB_-conf when mounting it from Windows or MacOS
3434

3535
**Link the openHAB share in Windows**
3636

3737
- Find you openHAB-Server via the network share functionality
38-
- User the share *openHAB*-conf to assign it to a network drive
38+
- User the share _openHAB_-conf to assign it to a network drive
3939

4040
**Link the openHAB share in macOS**
4141

@@ -49,7 +49,7 @@ In the main UI as an admin you can go to *Help & About* and will have the differ
4949

5050
**Finding it on Linux**
5151

52-
- Access the folder directly on the openHAB server at */etc/openhab*
52+
- Access the folder directly on the openHAB server at _/etc/openhab_
5353

5454
All methods reveal the following folders
5555

@@ -132,7 +132,7 @@ Pinching on a tablet or a touch bar also allows convenient zooming of the worksp
132132

133133
During development the log-block is lot very often which writes information into the log files.
134134

135-
- To be able to conveniently view your log files it is recommended to setup *frontail* which can be achieved easily via [openhabian-config](https://www.openhab.org/docs/installation/openhabian.html#optional-components)
135+
- To be able to conveniently view your log files it is recommended to setup _frontail_ which can be achieved easily via [openhabian-config](https://www.openhab.org/docs/installation/openhabian.html#optional-components)
136136
- Start `openhabian-config` on your server and choose option 20 and then option 21
137137
- After installation you can view your logs under [openhabian-config](http://myopenhab-server:9001) (adapt the server name)
138138
- **see [how to log](https://www.openhab.org/docs/administration/logging.html)**

0 commit comments

Comments
 (0)