[WR] Additional functionality (cloudflare#2461)

* SSL 4 SaaS info

* Added new file for events

* partial changes

* more progress

* First drafts of ssl for saas + create events

* Rough draft complete

* Wording tweak

* Tyler's initial feedback

* Tyler's other feedback

* Got all the feedback this time

* Small change to re-kick off build

* Tyler's last comment

* removed redundant fields

Author: kodster28

products/waiting-room/src/content/about/index.md

@@ -49,5 +49,5 @@ Access to certain features depends on a customer's [plan type](plans).
 ## Get started
 
 To learn how to use Cloudflare Waiting Rooms, check out:
-- The [setup guide](../get-started)
-- Various [how-to guides](../how-to)
+- The [setup guide](/get-started)
+- Various [how-to guides](/how-to)

products/waiting-room/src/content/additional-options/create-events.md

@@ -0,0 +1,77 @@
+---
+order: 3
+pcx-content-type: how-to
+---
+
+# Create scheduled events
+
+When you want to customize the behavior of a waiting room for a specific period of time — such as changing the queueing method or increasing the total active users — set up a **scheduled event**.
+
+Any properties set on the event will override the default property on the waiting room for the duration of the event.
+
+<Aside type="note">
+
+Only some customers can support scheduled events with their waiting rooms. For more details, see our <a href="/plans">Plans</a> page.
+
+</Aside>
+
+## Create an event
+
+At the moment, you can only create an event using the API.
+
+To create an event, make a [POST request](https://api.cloudflare.com/#waiting-room-create-event) including [required and optional parameters](#properties). Any properties set on the event will override the default property on the waiting room for the duration of the event.
+
+If you are using a [custom template](../customize-waiting-room#custom-waiting-room), you may want to add [relevant variables](https://api.cloudflare.com/#waiting-room-update-waiting-room) to your template (listed under the `json_response_enabled` parameter).
+
+<Aside type="note">
+
+If you need to create overlapping events, use different waiting rooms.
+
+</Aside>
+
+### Properties
+
+Though most properties are identical to those on a [regular waiting room](https://api.cloudflare.com/#waiting-room-properties), there are a few unique to [creating an event](https://api.cloudflare.com/#waiting-room-create-event):
+
+- `name` (required): Unique name with alphanumeric characters, hyphens, and underscores.
+- `event_start_time` (required): ISO 8601 timestamp that marks the start of the event. At this time, queued users will be processed with the event's configuration. Must occur at least 1 minute before `event_end_time`.
+- `event_end_time` (required): ISO 8601 timestamp that marks the end of the event.
+- `shuffle_at_event_start`: If **true** and `prequeue_start_time` is not null, users in the prequeue will be shuffled randomly at the `event_start_time`. Commonly used to ensure fairness if your event is using a [**FIFO** queueing method](#set-up-a-lottery).
+- `prequeue_start_time`: ISO 8601 timestamp that marks when to begin queueing all users before the event starts. Must occur at least **5 minutes before** `event_start_time`.
+- `description`: A text description providing more detail about the event.
+- `suspended`: If **true**, the event is ignored and traffic is handled based on the waiting room's normal configuration.
+
+## Set up a "lottery"
+
+Set up a "lottery" system to reward all users who enter into the queue prior to your event start time. 
+
+Users who reach your application **during the prequeue period** are [randomly assigned](/reference/queueing-methods#random) a place in line when the event starts. If the event uses [FIFO ordering](/reference/queueing-methods#first-in-first-out-fifo), users who reach your application **after the prequeue period** are assigned places after users from the prequeue.
+
+To set up a "lottery", include the [following parameters](#properties) in your API request:
+
+- `prequeue_start_time`
+- `shuffle_at_event_start`
+
+## Preview an event configuration
+
+Since some properties set on an event will override the default property of a waiting room for the duration of an event, you should use the API to [preview an event configuration](https://api.cloudflare.com/#waiting-room-preview-active-event-details) before it begins.
+
+This command shows you the event's configuration as if it were active, meaning that inherited fields from the waiting room will display their current values.
+
+## Edit an event
+
+To edit an event, use a [PATCH request](https://api.cloudflare.com/#waiting-room-patch-event).
+
+## Disable events
+
+You can disable an event by setting its `suspended` parameter to `true`.
+
+Additionally, events will not become active if a waiting room itself is **Disabled**. 
+
+## Other API commands
+
+Function | Command 
+---------|---------
+[Get event details](https://api.cloudflare.com/#waiting-room-event-details) | `GET`
+[List scheduled events](https://api.cloudflare.com/#waiting-room-list-events) | `GET`
+[Delete event](https://api.cloudflare.com/#waiting-room-delete-event) | `DELETE`

products/waiting-room/src/content/additional-options/customize-waiting-room.md

@@ -1,5 +1,5 @@
 ---
-order: 
+order: 1
 pcx-content-type: how-to
 ---
 

products/waiting-room/src/content/additional-options/embed-waiting-room-in-iframe.md

@@ -1,5 +1,5 @@
 ---
-order: 
+order: 4
 pcx-content-type: how-to
 ---
 

products/waiting-room/src/content/additional-options/mobile-traffic.md

@@ -1,5 +1,5 @@
 ---
-order: 
+order: 2
 pcx-content-type: how-to
 ---
 

products/waiting-room/src/content/additional-options/ssl-for-saas.md

@@ -0,0 +1,16 @@
+---
+order: 6
+pcx-content-type: reference
+---
+
+# Combine with SSL for SaaS
+
+If your application is using a custom hostname — meaning your SaaS provider is using [SSL for SaaS](https://developers.cloudflare.com/ssl/ssl-for-saas) — your application can support a waiting room.
+
+## Applications on Cloudflare
+
+If your application is already using Cloudflare, create a waiting room using the [normal process](/how-to/create-via-dashboard).
+
+## Applications not on Cloudflare
+
+If your application is not using Cloudflare, you need to ask your SaaS provider to [configure a waiting room](/how-to/create-via-dashboard) on their SSL for SaaS zone (using your custom hostname as the **Hostname** value).

products/waiting-room/src/content/plans/index.md

@@ -49,9 +49,15 @@ The features available for a waiting room depend on your plan type.
             <td>No</td>
             <td>Yes</td>
         </tr>
+        <tr>
+            <td><a href='/additional-options/create-events'>Scheduled events</a></td>
+            <td>No</td>
+            <td>No</td>
+            <td>Yes</td>
+        </tr>
    </tbody>
 </table>
 
 ## How do I get started?
 
-To get started with Waiting Room, review our [setup guide](/get-started).
+To get started with Waiting Room, review our [setup guide](/get-started).

products/waiting-room/src/content/reference/queueing-methods.md

@@ -22,7 +22,7 @@ Your waiting room orders visitors according to when they entered the waiting roo
 
 Technically, each user receives a [cookie](/reference/waiting-room-cookie) that contains a timestamp of when their request first hit an actively queueing waiting room. Cloudflare uses that timestamp to order visitors and provide the estimated wait time.
 
-Use this method when you want to reward visitors who get in the queue first and wait longer, such as for sneaker drops, memorabilia sales, etc.
+Use this method when you want to reward visitors who get in the queue first and wait longer.
 
 ## Random
 
@@ -32,6 +32,28 @@ When your application has open spots, your waiting room chooses visitors at rand
 
 Use this method when you want to distribute products or services more equitably. Earlier users have a better chance of exiting the waiting room before the estimated wait time because they have more chances to be selected.
 
+## API-only queueing methods
+
+The following queueing methods are only available via the API and are commonly used when you [create an event](/additional-options/create-events).
+
+<Aside type="note" header="Note:">
+
+If your waiting room is set to **Queue All**, all visitors will be queued, regardless of the chosen method.
+
+</Aside>
+
+### Passthrough
+
+Allow all traffic to pass immediately through your waiting room and into your application by setting its `queueing_method` to **passthrough**. If **Queue All** is enabled or an event is prequeueing, users will be queued in the waiting room.
+
+Use this setup when you only want to use your waiting room for events — where you can update the queueing method — and otherwise avoid queueing during low-traffic hours.
+
+### Reject
+
+Prevent any traffic from reaching your application by setting its `queueing_method` to **reject**. If **Queue All** is enabled or an event is prequeueing, users will **still be rejected** and see a static web page that does not refresh.
+
+Use this setup for event-only endpoints or to perform application maintenance.
+
 ## Changing queueing methods
 
 <ChangeQueueMethod/>