@@ -34,6 +34,9 @@ Tag Glossary
34
34
+-----------------------------------+---------------------------------------------+
35
35
| ``styling: small-multiples`` | |
36
36
+-----------------------------------+---------------------------------------------+
37
+ | ``styling: conditional`` |styling is determined programmatically by a |
38
+ | |condition being met |
39
+ +-----------------------------------+---------------------------------------------+
37
40
| | |
38
41
+-----------------------------------+---------------------------------------------+
39
42
| **Primary or relevant plot component** |
@@ -66,18 +69,28 @@ Tag Glossary
66
69
+-----------------------------------+---------------------------------------------+
67
70
| ``component: error`` | |
68
71
+-----------------------------------+---------------------------------------------+
72
+ | ``component: animation`` | |
73
+ +-----------------------------------+---------------------------------------------+
69
74
| | |
70
75
+-----------------------------------+---------------------------------------------+
71
76
| **Interactivity** |
72
77
+-----------------------------------+---------------------------------------------+
73
78
| ``interactivity: event handling`` | |
74
79
+-----------------------------------+---------------------------------------------+
80
+ | ``interactivity: click`` | |
81
+ +-----------------------------------+---------------------------------------------+
82
+ | ``interactivity: mouseover`` | |
83
+ +-----------------------------------+---------------------------------------------+
75
84
| ``interactivity: zoom`` | |
76
85
+-----------------------------------+---------------------------------------------+
77
86
| ``interactivity: pan`` | |
78
87
+-----------------------------------+---------------------------------------------+
79
88
| ``interactivity: brush`` | |
80
89
+-----------------------------------+---------------------------------------------+
90
+ | ``interactivity: drag`` | |
91
+ +-----------------------------------+---------------------------------------------+
92
+ | ``interactivity: scroll`` | |
93
+ +-----------------------------------+---------------------------------------------+
81
94
| | |
82
95
+-----------------------------------+---------------------------------------------+
83
96
| **Plot Type** |
@@ -96,35 +109,41 @@ Tag Glossary
96
109
+-----------------------------------+---------------------------------------------+
97
110
| ``plot type: specialty`` | |
98
111
+-----------------------------------+---------------------------------------------+
99
- | ``plot type: `` | |
112
+ | ``plot type: scatter`` | |
100
113
+-----------------------------------+---------------------------------------------+
101
114
102
115
103
116
*2. Structural tags: what format is the example? What context can we provide? *
104
117
105
- +-----------------------+-------------------------------------------------------------------+
106
- | ``tag`` | use case |
107
- +=======================+===================================================================+
108
- | ``level: reference`` |reference docs like "marker reference" or "list of named colors" |
109
- | | - dense collection of short-format information |
110
- | | - well-defined scope, accessible information |
111
- +-----------------------+-------------------------------------------------------------------+
112
- | ``level`` |level refers to how much context/background the user will need |
113
- +-----------------------+-------------------------------------------------------------------+
114
- | ``level: beginner`` |concepts are standalone, self-contained, require only one module |
115
- +-----------------------+-------------------------------------------------------------------+
116
- | ``level: intermediate``|concepts may require knowledge of other modules, have dependencies |
117
- +-----------------------+-------------------------------------------------------------------+
118
- | ``level: advanced`` |concepts require multiple modules and have dependencies |
119
- +-----------------------+-------------------------------------------------------------------+
118
+ +----------------------------+-------------------------------------------------------------------+
119
+ | ``tag`` | use case |
120
+ +============================+===================================================================+
121
+ | ``level`` |level refers to how much context/background the user will need |
122
+ +----------------------------+-------------------------------------------------------------------+
123
+ | ``level: beginner`` |concepts are standalone, self-contained, require only one module |
124
+ +----------------------------+-------------------------------------------------------------------+
125
+ | ``level: intermediate`` |concepts may require knowledge of other modules, have dependencies |
126
+ +----------------------------+-------------------------------------------------------------------+
127
+ | ``level: advanced`` |concepts require multiple modules and have dependencies |
128
+ +----------------------------+-------------------------------------------------------------------+
129
+ | ``purpose`` |what's it here for? |
130
+ +----------------------------+-------------------------------------------------------------------+
131
+ | ``purpose: storytelling`` |storytelling exemplar -- build a visual argument |
132
+ +----------------------------+-------------------------------------------------------------------+
133
+ | ``purpose: reference`` |reference docs like "marker reference" or "list of named colors" |
134
+ | | - dense collection of short-format information |
135
+ | | - well-defined scope, accessible information |
136
+ +----------------------------+-------------------------------------------------------------------+
137
+ | ``purpose: fun`` |just for fun! |
138
+ +----------------------------+-------------------------------------------------------------------+
120
139
121
140
*3. Domain tags: what discipline(s) might seek this example consistently? *
122
141
123
142
Note: it's futile to draw fences around "who owns what", and that's not the point of domain tags. Domain tags help groups of people to privately organize relevant information, and so are not displayed publicly. See below for a list of existing domain tags. If you don't see the one you're looking for and you think it should exist, consider proposing it.
124
143
125
144
+-------------------------------+----------------------------------------+
126
145
| ``tag`` | use case |
127
- +=======================+ ================================================+
146
+ +===============================+ ========================================+
128
147
| ``domain`` |for whom is the example relevant? |
129
148
+-------------------------------+----------------------------------------+
130
149
| ``domain: cartography`` | |
@@ -142,14 +161,19 @@ Note: it's futile to draw fences around "who owns what", and that's not the poin
142
161
143
162
*4. Internal tags: what information is helpful for maintainers or contributors? *
144
163
145
- +---------------------------+-----------------------------------------------------------------------+
146
- | ``tag`` | use case |
147
- +===========================+=======================================================================+
148
- | ``internal: low bandwidth``|allows users to filter out bandwidth-intensive examples like animations|
149
- +---------------------------+-----------------------------------------------------------------------+
150
- | ``internal: untagged`` |allows docs contributors to easily find untagged examples |
151
- +---------------------------+-----------------------------------------------------------------------+
152
- | ``internal: deprecated`` |examples containing deprecated functionality or concepts |
153
- +---------------------------+-----------------------------------------------------------------------+
154
- | ``internal: needs-review`` |example needs to be reviewed for accuracy or pedagogical value |
155
- +---------------------------+-----------------------------------------------------------------------+
164
+ +-------------------------------+-----------------------------------------------------------------------+
165
+ | ``tag`` | use case |
166
+ +===============================+=======================================================================+
167
+ | ``internal: low bandwidth`` |allows users to filter out bandwidth-intensive examples like animations|
168
+ +-------------------------------+-----------------------------------------------------------------------+
169
+ | ``internal: untagged`` |allows docs contributors to easily find untagged examples |
170
+ +-------------------------------+-----------------------------------------------------------------------+
171
+ | ``internal: deprecated`` |examples containing deprecated functionality or concepts |
172
+ +-------------------------------+-----------------------------------------------------------------------+
173
+ | ``internal: needs-review`` |example needs to be reviewed for accuracy or pedagogical value |
174
+ +-------------------------------+-----------------------------------------------------------------------+
175
+ | ``internal: outstanding-todo`` |example has an unfinished to-do |
176
+ +-------------------------------+-----------------------------------------------------------------------+
177
+ | ``internal: too-much`` |the example should be refined, split into multiple examples, or |
178
+ | |reformatted into a tutorial or reference |
179
+ +-------------------------------+-----------------------------------------------------------------------+
0 commit comments