Migrate to Docusaurus

I wasn't thrilled with mkdocs. It wasn't amazing to use, and didn't look
all that professional.

Author: jgayfer

.gitignore

@@ -0,0 +1,20 @@
+# Dependencies
+/node_modules
+
+# Production
+/build
+
+# Generated files
+.docusaurus
+.cache-loader
+
+# Misc
+.DS_Store
+.env.local
+.env.development.local
+.env.test.local
+.env.production.local
+
+npm-debug.log*
+yarn-debug.log*
+yarn-error.log*

Pipfile

@@ -0,0 +1,3 @@
+module.exports = {
+  presets: [require.resolve('@docusaurus/core/lib/babel/preset')],
+};

Pipfile.lock

@@ -0,0 +1,13 @@
+import React from 'react'
+import useBaseUrl from '@docusaurus/useBaseUrl'
+
+export default function Figure({ src, caption }) {
+  return (
+    <figure style={{ 'margin': '30px 0' }}>
+      <div style={{ 'display': 'flex', 'justify-content': 'center' }}>
+        <img src={useBaseUrl(src)} alt={caption} style={{ 'display': 'auto', 'border-radius': '10px', 'max-width': '100%', 'width': '600px' }} />
+      </div>
+      <figcaption style={{ 'text-align': 'center', 'font-style': 'italic' }}>{caption}</figcaption>
+    </figure>
+  )
+}

babel.config.js

@@ -1,4 +1,14 @@
-# Frequently Answered Questions
+---
+title: FAQ
+sidebar_position: 2
+slug: /faq
+---
+
+# Frequently answered questions
+
+These are some of the questions we get most often.
+
+If you're not able to resolve an issue, please get in touch on our [Discord server](https://discord.com/invite/dMnZt6P).
 
 ---
 

docs/figure.jsx

@@ -0,0 +1,13 @@
+import React from 'react'
+import useBaseUrl from '@docusaurus/useBaseUrl'
+
+export default function Figure({ src, caption }) {
+  return (
+    <figure style={{ 'margin': '30px 0' }}>
+      <div style={{ 'display': 'flex', 'justify-content': 'center' }}>
+        <img src={useBaseUrl(src)} alt={caption} style={{ 'display': 'auto', 'border-radius': '10px', 'max-width': '100%', 'width': '600px' }} />
+      </div>
+      <figcaption style={{ 'text-align': 'center', 'font-style': 'italic' }}>{caption}</figcaption>
+    </figure>
+  )
+}

docs/faq.md docs/guides/faq.mdxdocs/faq.md renamed to docs/guides/faq.mdx

@@ -1,9 +1,14 @@
+---
+sidebar_position: 1
+slug: /
+---
+
 # Getting started
 
 Getting started with Apollo is quick and easy.
 
 1. [Invite Apollo to your server](https://discord.com/api/oauth2/authorize?client_id=475744554910351370&permissions=36776045648&scope=applications.commands%20bot)
-2. Create your first event with the [`/event`](/creating-events/) command
+2. Create your first event with the [`/event`](/creating_events/) command
     - Apollo will then DM you a list of questions about your event
     - Once finished, Apollo will provide a link to your newly created event
 3. RSVP to the event by clicking one of the event buttons

docs/guides/figure.jsx

@@ -0,0 +1,2 @@
+label: Guides
+collapsed: false

docs/getting_started.md docs/guides/getting_started.mdxdocs/getting_started.md renamed to docs/guides/getting_started.mdx

@@ -1,3 +1,9 @@
+---
+description: Manage which roles are assigned to attendees.
+slug: /attendee_roles
+sidebar_position: 6
+---
+
 # Attendee roles
 
 [Apollo Premium](https://apollo.fyi/premium) allows event organizers to
@@ -12,9 +18,10 @@ Once an attendee role is setup, attendees will be given the role when they sign
 up for the event. The role will be removed from attendees when they remove their
 signup, or the event is deleted.
 
-!!! warning "Permission check"
-    Apollo must have the `Manage Roles` permission in order to assign roles to
-    attendees.
+:::warning Permission check
+Apollo must have the `Manage Roles` permission in order to assign roles to
+attendees.
+:::
 
 ## Temporary attendee roles
 When using a temporary role, Apollo will create a role in the format of:
@@ -36,9 +43,10 @@ new events by default with `/settings temp_roles on`.
 
 This command requires the `Manage Server` permission to invoke.
 
-!!! note
-    If temporary roles are enabled by default, they can still be configured on a
-    per event basis.
+:::note
+If temporary roles are enabled by default, they can still be configured on a
+per event basis.
+:::
 
 ## Persistent attendee roles
 
@@ -47,45 +55,50 @@ role to attendees as they update their responses.
 
 When the event is deleted, the role will be removed from all attendees.
 
-!!! note
-    Apollo will not allow users to assign a persistent attendee role if they
-    don't personally have permission to `Manage Roles` on the server.
+:::note
+Apollo will not allow users to assign a persistent attendee role if they
+don't personally have permission to `Manage Roles` on the server.
+:::
 
-!!! warning
-    When using a persistent attendee role, the role must be **below**
-    Apollo's highest role in the role hierarchy list, otherwise Apollo will not
-    be able to add the role to attendees.
+:::warning
+When using a persistent attendee role, the role must be **below**
+Apollo's highest role in the role hierarchy list, otherwise Apollo will not
+be able to add the role to attendees.
+:::
 
 ### Multiple events
 
 When multiple events share the same persistent attendee role, the role is only
 removed from an attendee when they are not signed up for any events with the
 persistent attendee role.
 
-!!! example
-    John signs up for two events, both of which have the same persistent
-    attendee role.
+:::tip Example
+John signs up for two events, both of which have the same persistent
+attendee role.
 
-    John's attendee role will be removed when his responses are removed from
-    both events. Response removal can occur by John manually removing his
-    signup, but it will also occur if the event is deleted.
+John's attendee role will be removed when his responses are removed from
+both events. Response removal can occur by John manually removing his
+signup, but it will also occur if the event is deleted.
+:::
 
 ## Using attendee roles
 
-!!! info inline end
-    Attendee roles are granted to users who sign up for signup options that have
-    **reminders enabled**.
-
-    By default, only the **Accepted** option has reminders enabled, but this can
-    be configured on a per event basis.
-
 An attendee role can be configured during event creation on the advanced options
 prompt (the last prompt when creating an event).
 
 When the attendee role option is selected, you’ll have the option to let Apollo
 create a temporary attendee role, or to specify an existing role to assign to
 attendees.
 
+:::note
+Attendee roles are granted to users who sign up for signup options that have
+**reminders enabled**.
+
+By default, only the **Accepted** option has reminders enabled, but this can
+be configured on a per event basis.
+:::
+
+
 ## Modify attendee roles
 
 Attendee roles can be fully modified for both single and recurring
@@ -94,6 +107,7 @@ events.
 When an event attendee role is added, removed, or updated, we’ll go through the
 list of attendees on the event to ensure that their attendee role is correct.
 
-!!! note
-    When updating an attendee role for an event with a large number of
-    attendees, it can take a minute to update everyone’s role.
+:::note
+When updating an attendee role for an event with a large number of
+attendees, it can take a minute to update everyone’s role.
+:::