-
Notifications
You must be signed in to change notification settings - Fork 0
/
rule_template_generic.yml
88 lines (76 loc) · 3.26 KB
/
rule_template_generic.yml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
# This file is a bare-bones template that you can quickly copy/paste to create and edit rulesets. If you'd like to read a more in-depth explanation of how YAML rulesets work, check out `rule_template_with_examples.yml`.
description: PAGE DESCRIPTION
content:
# === don't duplicate any of the keys above this line—each ruleset file should only have a single `description` key and a single `content` key ===
# === the keys below this line can be copy/pasted ad infinitum to create rulesets as long or as short as you'd like ===
- section: SECTION NAME
sectionrules:
# copy/paste `section`/`sectionrules` blocks as needed—just make sure to include each section's rules within a single `sectionrules` key
- rule: | # copy/paste 'rule' blocks as needed
### RULE WITH A TITLE<br>
CONTENT OF THE RULE
audience: [tw, dev, mktg] # add/delete audiences for each rule as needed, just make sure they're contained within a single array
- rule: |
CONTENT OF A RULE WITH NO TITLE<br>
HOWEVER, THIS RULE STILL HAS MULTIPLE LINES
audience: [tw, dev, mktg]
- rule: |
### THIS RULE HAS A TITLE AND ALSO EXAMPLES<br>
SEE BELOW FOR THE EXAMPLES
examples: # copy/paste individual list items for each example as needed; each `examples` key can contain one or more list items
- |
AN EXAMPLE
- |
ANOTHER EXAMPLE<br>
THIS EXAMPLE HAS MULTIPLE LINES
audience: [tw, dev, mktg]
- rule: |
### THIS RULE HAS A TITLE AND EXAMPLES AND IS 'FEATURED'<br>
THE 'FEATURED' LINK IS INCLUDED BELOW AND USES LIQUID TAGS IN ITS URL
examples:
- |
AN EXAMPLE
- |
ANOTHER EXAMPLE<br>
THIS EXAMPLE HAS MULTIPLE LINES
audience: [tw, dev, mktg]
featured: | # copy/paste `featured` blocks as needed, just make sure to swap out "SECTION" and "HEADING-GOES-HERE" with the correct values
[A SHORT DESCRIPTION OF THE RULE.]({{site.baseurl}}{{page.permalink}}SECTION/#HEADING-GOES-HERE)
- section: ANOTHER SECTION NAME
sectionrules:
- rule: |
### THIS RULE HAS A TITLE AND EXAMPLES AND IS 'FEATURED'<br>
THE 'FEATURED' LINK IS INCLUDED BELOW AND USES LIQUID TAGS IN ITS URL
examples:
- |
AN EXAMPLE
- |
ANOTHER EXAMPLE<br>
THIS EXAMPLE HAS MULTIPLE LINES
audience: [tw, dev, mktg]
featured: |
[A SHORT DESCRIPTION OF THE RULE.]({{site.baseurl}}{{page.permalink}}SECTION/#HEADING-GOES-HERE)
- rule: |
### THIS RULE HAS A TITLE AND EXAMPLES AND IS 'FEATURED'<br>
THE 'FEATURED' LINK IS INCLUDED BELOW AND USES LIQUID TAGS IN ITS URL
examples:
- |
AN EXAMPLE
- |
ANOTHER EXAMPLE<br>
THIS EXAMPLE HAS MULTIPLE LINES
audience: [tw, dev, mktg]
featured: |
[A SHORT DESCRIPTION OF THE RULE.]({{site.baseurl}}{{page.permalink}}SECTION/#HEADING-GOES-HERE)
- rule: |
### THIS RULE HAS A TITLE AND EXAMPLES AND IS 'FEATURED'<br>
THE 'FEATURED' LINK IS INCLUDED BELOW AND USES LIQUID TAGS IN ITS URL
examples:
- |
AN EXAMPLE
- |
ANOTHER EXAMPLE<br>
THIS EXAMPLE HAS MULTIPLE LINES
audience: [tw, dev, mktg]
featured: |
[A SHORT DESCRIPTION OF THE RULE.]({{site.baseurl}}{{page.permalink}}SECTION/#HEADING-GOES-HERE)