Skip to content
This repository was archived by the owner on May 5, 2025. It is now read-only.

Commit c5123ce

Browse files
Create Rule Page (#137)
1 parent 32c38c0 commit c5123ce

File tree

2 files changed

+32
-5
lines changed

2 files changed

+32
-5
lines changed

docs/sources/twilio.md

Lines changed: 1 addition & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -3,11 +3,7 @@ This event source is to be deployed and then registered as a webhook via Twilio
33

44
## Prerequisite(s)
55

6-
* Twilio Account
7-
8-
### Twilio Acoount
9-
10-
A Twilio account (trial or paid) is required.
6+
- A Twilio account (trial or paid)
117

128
## Deploying an Instance of the Source
139

templates/rules.md

Lines changed: 31 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,31 @@
1+
# Rules
2+
3+
## TriggerMesh
4+
5+
Please make sure to use capital letters for TriggerMesh known elements like Bridges, Sources, Targets, use `TriggerMesh` and not `Triggermesh`.
6+
7+
## Unordered Lists (Bullet Lists)
8+
9+
For Unorderd Lists (a.k.a. Bullet Lists) we would like to use of `-` instead of `*`.
10+
11+
`-` would be the more logical choice, since it eliminates the ambiguity between `*` (bulltet point), `* *` (italic) and `**` `**` (bold).
12+
13+
### Example Bullet List
14+
15+
- Example
16+
- Example
17+
- Example
18+
19+
## Ordered Lists (Number Lists)
20+
21+
For Ordered Lists (a.k.a. Number Lists) we would like to use `1. 1. 1.` instead of `1. 2. 3.` for listing numbers.
22+
23+
`1. 1. 1.` is actually the recommended way to create numbered lists in Markdown. The generated page will have the correct numbering, not `1. 1. 1.`....
24+
25+
The advantage is that you can add/remove elements to a list without having to renumber everything manually.
26+
27+
### Example Number List
28+
29+
1. Example
30+
1. Example
31+
1. Example

0 commit comments

Comments
 (0)