Merge pull request #7 from DevOpsDaysChicago/upgrade

Upgrade to docusaurus 3

docs/organizing-team-administration/onboarding-team-members.md

@@ -28,17 +28,17 @@ sidebar_position: 2
 ### Example Welcome Email
 
 
-> Hi {{Person}}! After reviewing with the team, we would love to invite you to join the DevOpsDays Chicago organizing team! If you are interested in doing so, please fill out this form here - {{ FormLink }}
+> Hi `Person`! After reviewing with the team, we would love to invite you to join the DevOpsDays Chicago organizing team! If you are interested in doing so, please fill out this form here - `FormLink`
 > 
 > (that form contains a few details on expectations and gives me some info we need!)
 > 
 > ******************************************************
 > 
 > To level-set a few things about what it means to be an organizer:
 > 
-> - we have regular meetings, which generally take place over Zoom (although we sometimes meet in person, just to keep in touch). These meetings are currently every other Thursday at noon central time (next meeting is {{ NextMeetingDate }} to help out with the "every other"). As the event gets closer, the meetings will become weekly. You do not need to attend every meeting, but it is expected to try to attend as many as possible. 
+> - we have regular meetings, which generally take place over Zoom (although we sometimes meet in person, just to keep in touch). These meetings are currently every other Thursday at noon central time (next meeting is `NextMeetingDate` to help out with the "every other"). As the event gets closer, the meetings will become weekly. You do not need to attend every meeting, but it is expected to try to attend as many as possible. 
 > - we have a dedicated Slack workspace for the organizing team. It is expected to check this Slack at least every other day M-F (if you are traveling or on PTO/vacation, this doesn't apply)
 > - you will be set up with a devopsdayschi.org email address. It is expected that you will check this email at once a day M-F, and acknowledge/reply to messages sent to you there. you can, of course, forward this to another email address if you like.
-> - Depending upon the committee(s) you choose to take part in, the amount of effort for being on this team will vary throughout the months leading up to the event. However, it is expected that as an organizer you will be available all-day on {{EventDays}} (the days of the event), and usually we also plan to work together on {{DayBeforeEvent}} (the day before the event). 
+> - Depending upon the committee(s) you choose to take part in, the amount of effort for being on this team will vary throughout the months leading up to the event. However, it is expected that as an organizer you will be available all-day on `EventDays` (the days of the event), and usually we also plan to work together on `DayBeforeEvent` (the day before the event). 
 
-> Still interested? Fill out this form {{ FormLink }} and we can go from there! Any questions you might have, please let me know!
+> Still interested? Fill out this form `FormLink` and we can go from there! Any questions you might have, please let me know!

docs/policies/communication-policies.md

@@ -38,7 +38,7 @@ Participation in the global devopsdays organizer Slack workspace is optional, bu
 
 ## Email
 
-All DevOpsDays Chicago organizers are set up with a Google Apps account under the devopsdayschi.org domain. It is at your discretion if you choose to manage your email in that inbox, or to forward mail sent to you to another email address. By default, all meeting invites for the team will be sent to your devopsdayschi.org email address/calendar, but you can feel free to forward those invites to the calendar of your choosing, or to invite an additional calendar of your choosing to that invite. The devopsdays.org email aliases (including <[email protected]>, etc) will only forward to your devopsdayschi.org email address.
+All DevOpsDays Chicago organizers are set up with a Google Apps account under the devopsdayschi.org domain. It is at your discretion if you choose to manage your email in that inbox, or to forward mail sent to you to another email address. By default, all meeting invites for the team will be sent to your devopsdayschi.org email address/calendar, but you can feel free to forward those invites to the calendar of your choosing, or to invite an additional calendar of your choosing to that invite. The devopsdays.org email aliases (including `[email protected]`, etc) will only forward to your devopsdayschi.org email address.
 
 Regardless of how you choose to manage this email, the following expectations exist:
 

docs/policies/expense-policy.md

@@ -6,16 +6,16 @@ description: Policies  and expectations for expenses
 
 If you have an expense related to DevOpsDays Chicago, this is the policy around approvals and reimbursements.
 
-The email alias <[email protected]> should be used for all approvals and reimbursement requests. This email address forwards to the authorized expense approvers for DevOpsDays Chicago as well as to Laura Wickett of ConferenceOps.
+The email alias `[email protected]` should be used for all approvals and reimbursement requests. This email address forwards to the authorized expense approvers for DevOpsDays Chicago as well as to Laura Wickett of ConferenceOps.
 
 ## Pre-approval
 
-If the expense is over $400, it is recommended that you obtain pre-approval from the Expense Approvers group. Send an email to <[email protected]> with information on what the expense is for, and what the estimated cost is. This is not required, but it is highly recommended to avoid issues when submitting for reimbursement. Please be clear in the email that this is a request for pre-approval, so that Laura does not think you are submitting an expense for reimbursement.
+If the expense is over $400, it is recommended that you obtain pre-approval from the Expense Approvers group. Send an email to `[email protected]` with information on what the expense is for, and what the estimated cost is. This is not required, but it is highly recommended to avoid issues when submitting for reimbursement. Please be clear in the email that this is a request for pre-approval, so that Laura does not think you are submitting an expense for reimbursement.
 
 ## Payment by ConferenceOps for an expense
 
-If you do not wish to use your own personal funds/credit card for an expense, you can request that Laura from ConferenceOps arrange the payment for you. Please send the necessary information for this payment (including any invoices or other record for the amount) to <[email protected]>, and request that Laura provide the payment.. After two approvals from the expense approval team, Laura will arrange the payment.
+If you do not wish to use your own personal funds/credit card for an expense, you can request that Laura from ConferenceOps arrange the payment for you. Please send the necessary information for this payment (including any invoices or other record for the amount) to `[email protected]`, and request that Laura provide the payment.. After two approvals from the expense approval team, Laura will arrange the payment.
 
 ## Reimbursement
 
-If you have paid for an expense with your own personal funds/credit card, please send receipts to <[email protected]> for approval. After two approvals from the expense approval team, Laura will reimburse you using one of the approved reimbursement methods (Zelle Quickpay, PayPal, or a paper check mailed to you)
+If you have paid for an expense with your own personal funds/credit card, please send receipts to `[email protected]` for approval. After two approvals from the expense approval team, Laura will reimburse you using one of the approved reimbursement methods (Zelle Quickpay, PayPal, or a paper check mailed to you)

docs/sponsorship/sponsor-committee-responsibilities.md

@@ -8,9 +8,9 @@ sidebar_position: 3
 
 - [Follow templates in Drive](https://drive.google.com/open?id=1eNnu2klIXmfJzl0H4p8IE3RXXCzkNiBZQ3sNjDyVZQ4). If in doubt, chat with other organizers in Slack
 
-- Reply to the email, cc sponsorships <[email protected]> for transparency
+- Reply to the email, cc sponsorships `[email protected]` for transparency
 
-- To pay, they can pay directly via the website using a credit card, or to create an invoice and/or get a new W9 email Laura: <[email protected]>
+- To pay, they can pay directly via the website using a credit card, or to create an invoice and/or get a new W9 email Laura: `[email protected]`
 
 - Ask for a hi-res logo for website / slides
 
@@ -20,7 +20,7 @@ sidebar_position: 3
 
 ## Contact previous sponsors until you hear "no"
 
-- Work through a list in Trello, such as "2020 new / needs work 🕵🏻‍♀: <https://trello.com/b/RYTq2DG2/sponsorship>
+- Work through a list in Trello, such as "2020 new / needs work 🕵🏻‍♀: https://trello.com/b/RYTq2DG2/sponsorship
 
 - [Follow templates in Drive](https://drive.google.com/open?id=1eNnu2klIXmfJzl0H4p8IE3RXXCzkNiBZQ3sNjDyVZQ4). If in doubt, chat with other organizers in Slack
 
@@ -44,7 +44,7 @@ sidebar_position: 3
 
 - [Follow templates in Drive](https://drive.google.com/open?id=1eNnu2klIXmfJzl0H4p8IE3RXXCzkNiBZQ3sNjDyVZQ4). If in doubt, chat with other organizers in Slack
 
-- Reply to the email, cc sponsorships [email protected] for transparency
+- Reply to the email, cc sponsorships `[email protected]` for transparency
 
 - Follow up when CFP is open and ask for local submissions
 
@@ -54,7 +54,7 @@ sidebar_position: 3
 
 - Specify only what comes with the sponsorship and do not negotiate for special deals.
 
-- Remind sponsors repeatedly about global DevOpsDays rules such as no sponsored talks and contact information is never shared. See <https://devopsdays.org/organizing> for more.
+- Remind sponsors repeatedly about global DevOpsDays rules such as no sponsored talks and contact information is never shared. See https://devopsdays.org/organizing for more.
 
 - Be consistent about what comes with sponsorships.
 

docs/sponsorship/sponsor-comms.md

@@ -2,7 +2,7 @@
 sidebar_position: 5
 ---
 
-# Sponsor communications =
+# Sponsor communications
 
 TODO
 

docs/tools-and-services/pretalx.md

@@ -0,0 +1,5 @@
+---
+sidebar_position: 4
+---
+
+# Pretalx (CFP and program)

docs/tools-and-services/pretix/_category_.json

@@ -0,0 +1,8 @@
+{
+  "label": "Pretix (Ticketing)",
+  "position": 99,
+  "link": {
+    "type": "generated-index",
+    "description": "Pretix is the ticketing system"
+  }
+}

docs/tools-and-services/pretix/pretix.md

@@ -0,0 +1,7 @@
+---
+sidebar_position: 4
+---
+
+# Pretix Configuration
+
+hi

docs/tickets.md → docs/tools-and-services/pretix/tickets.md

@@ -2,9 +2,7 @@
 sidebar_position: 9
 ---
 
-# Ticketing
-
-## Ticket types
+# Ticket types
 
 We create ticket types in the following categories, which are used to control "how many" tickets of each type, as well as potentially for branding on the badges themselves.
 

docs/tools-and-services/sendy.md

@@ -0,0 +1,5 @@
+---
+sidebar_position: 4
+---
+
+# Sendy (Mailing lists)

docusaurus.config.js

@@ -1,8 +1,9 @@
 // @ts-check
 // Note: type annotations allow type checking and IDEs autocompletion
 
-const lightCodeTheme = require('prism-react-renderer/themes/github');
-const darkCodeTheme = require('prism-react-renderer/themes/dracula');
+const {themes} = require('prism-react-renderer');
+const lightCodeTheme = themes.github;
+const darkCodeTheme = themes.dracula;
 
 /** @type {import('@docusaurus/types').Config} */
 const config = {
@@ -37,7 +38,8 @@ const config = {
           // Please change this to your repo.
           // Remove this to remove the "edit this page" links.
           editUrl:
-            'https://github.com/facebook/docusaurus/tree/main/packages/create-docusaurus/templates/shared/',
+            'https://github.com/devopsdayschi/dodchi-docs/tree/main/packages/create-docusaurus/templates/shared/',
+          sidebarPath: './sidebars.js',
         },
         blog: false,
         theme: {
@@ -77,3 +79,28 @@ const config = {
 };
 
 module.exports = config;
+
+// export default {
+//   plugins: [
+//     [
+//       '@docusaurus/plugin-content-docs',
+//       {
+//         async sidebarItemsGenerator({
+//           defaultSidebarItemsGenerator,
+//           numberPrefixParser,
+//           item,
+//           version,
+//           docs,
+//           categoriesMetadata,
+//           isCategoryIndex,
+//         }) {
+//           // Example: return an hardcoded list of static sidebar items
+//           return [
+//             {type: 'doc', id: 'doc1'},
+//             {type: 'doc', id: 'doc2'},
+//           ];
+//         },
+//       },
+//     ],
+//   ],
+// };

package.json

@@ -14,16 +14,17 @@
     "write-heading-ids": "docusaurus write-heading-ids"
   },
   "dependencies": {
-    "@docusaurus/core": "2.2.0",
-    "@docusaurus/preset-classic": "2.2.0",
-    "@mdx-js/react": "^1.6.22",
+    "@docusaurus/core": "3.0.0",
+    "@docusaurus/preset-classic": "3.0.0",
+    "@mdx-js/react": "^3.0.0",
     "clsx": "^1.2.1",
-    "prism-react-renderer": "^1.3.5",
-    "react": "^17.0.2",
-    "react-dom": "^17.0.2"
+    "prism-react-renderer": "^2.1.0",
+    "react": "^18.0.0",
+    "react-dom": "^18.2.0"
   },
   "devDependencies": {
-    "@docusaurus/module-type-aliases": "2.2.0"
+    "@docusaurus/module-type-aliases": "3.0.0",
+    "@docusaurus/types": "3.0.0"
   },
   "browserslist": {
     "production": [
@@ -38,6 +39,6 @@
     ]
   },
   "engines": {
-    "node": ">=16.14"
+    "node": ">=18.04"
   }
 }

sidebars.js

@@ -1,33 +1,9 @@
-/**
- * Creating a sidebar enables you to:
- - create an ordered group of docs
- - render a sidebar for each doc of that group
- - provide next/previous navigation
-
- The sidebars can be generated from the filesystem, or explicitly defined here.
-
- Create as many sidebars as you want.
- */
-
-// @ts-check
-
-/** @type {import('@docusaurus/plugin-content-docs').SidebarsConfig} */
-const sidebars = {
-  // By default, Docusaurus generates a sidebar from the docs folder structure
-  tutorialSidebar: [{type: 'autogenerated', dirName: '.'}],
-
-  // But you can create a sidebar manually
-  /*
-  tutorialSidebar: [
-    'intro',
-    'hello',
-    {
-      type: 'category',
-      label: 'Tutorial',
-      items: ['tutorial-basics/create-a-document'],
-    },
-  ],
-   */
-};
-
-module.exports = sidebars;
+/** @type {import('@docusaurus/plugin-content-docs').SidebarsConfig} */
+export default {
+  dodchi: [
+    {
+      type: 'autogenerated',
+      dirName: '.',
+    },
+  ],
+};