In the JS UI, turn each category of Activity into a collapsible section to save space #147

static/apidocs/openapi.yml

@@ -917,10 +917,11 @@ components:
     ActivityType:
       type: string
       enum:
-        - WORLDWIDE
+        - TRADITIONAL
+        - ADVENTURE
         - REGIONAL
         - EVENT
-      example: WORLDWIDE
+      example: TRADITIONAL
 
     ActivityNameIncludingNoSig:
       oneOf:
@@ -1597,16 +1598,16 @@ components:
         sig_type:
           type: boolean
           description: >
-            Whether the activity is worldwide, regional, or for a specific event. Generally for Spothole's own
-            internal use, clients probably won't need this. Used to group them in the web UI. Still named
-            "sig_type" in the API for backwards compatibility.
+            Whether the activity is traditional (e.g. EME), adventure (e.g. POTA), regional (e.g. WAB), or for a
+            specific event (e.g. MOTA). Generally for Spothole's own internal use, clients probably won't need this.
+            Used to group them in the web UI. Still named "sig_type" in the API for backwards compatibility.
           $ref: "#/components/schemas/ActivityType"
         comment_names:
           type: array
           description: >
             Names by which this activity may be referred to in cluster spot comments. Most activities have a
             single entry matching their programme name (e.g. ["POTA"]), but some have none (where
-            the name is ambiguous with other activities, such as Tiles and Toilets on the Air) or multiple
+            the name is ambiguous with other activities, such as "TOTA" for Tiles and Toilets on the Air) or multiple
             entries (e.g. WWBOTA accepts both "WWBOTA" and "BOTA" since the latter is often used).
           items:
             type: string