docs: add mermaid diagrams redo

docs/lightning-talks/processes/project-workflow.md

@@ -35,23 +35,100 @@ tags:
 
 The function of the Lightning Talks Event is to allow opportunities for members of the community to have an intimate space to present on a tech topic for 5-15 minutes. When live-streaming as a members-only event, speakers can feel more comfortable as it's _their_ community listening and watching. However, their is still opportunity to impact a larger audience once the videos have been processed and put up on YouTube.
 
-### Specifics
+Below is the workflow for the Lightning Talks Event.
 
-- 5-15 minutes on one topic
-- Slides are optional
-- Mentorship is provided if requested
-
-### Timeline
+### Timeline {#timeline-section}
 
 #### Call for coordinators, mentors, and other teammates
 
+<details>
+  <summary>📊 View Planning Phase Diagram</summary>
+  <div style={{marginTop: '1rem'}}>
+
+```mermaid
+%%{init: {'theme':'base', 'themeVariables': {'fontSize':'24px', 'fontFamily':'arial'}}}%%
+flowchart LR
+  %% Left Column - Team Forming
+  subgraph A["👥 Team Forming"]
+    direction TB
+    A1["📢 Call for Team Members"]
+    A2["👥 Onboard New Team"]
+    A3["📝 Assign Coordinators"]
+    A4["📋 Review Responsibilities"]
+    A1 --> A2 --> A3 --> A4
+  end
+
+  %% Right Column - Initial Planning
+  subgraph B["📋 Initial Planning"]
+    direction TB
+    B1["📅 Set Timeline"]
+    B2["🎯 Define Goals"]
+    B3["📝 Create Checklist"]
+    B1 --> B2 --> B3
+  end
+
+  %% Flow between columns
+  A4 --> B1
+
+  %% Styling
+  classDef default fill:#f5f5f5,stroke:#2e8555,stroke-width:3px,color:#1a1a1a,padding:15px;
+  classDef process fill:#e6f3ed,stroke:#2e8555,stroke-width:3px,color:#1a1a1a;
+  class A,B process;
+```
+
+  </div>
+</details>
+
 - Happens before the cfp to create a smoother onboarding process
 - Roles are clarified and onboarding occurs (specify what this looks like)
   - Early assign coordinators based on input (ie, Bekah will take Group 1)
     - This will allow quick response times.
 - Team meeting
 
-#### CFP
+### CFP (Call For Proposals)
+
+<details>
+  <summary>📋 View CFP Process Diagram</summary>
+  <div style={{marginTop: '1rem'}}>
+
+```mermaid
+%%{init: {'theme':'base', 'themeVariables': {'fontSize':'26px', 'fontFamily':'arial'}}}%%
+flowchart LR
+  %% Left Column - Proposal Collection
+  subgraph A["📬 Proposal Collection"]
+    direction TB
+    A1["📣 CFP Opens"]
+    A2["🧾 Collect Proposals"]
+    A3{"Enough Proposals?"}
+    A4["📢 Extend CFP Period"]
+    A1 --> A2 --> A3
+    A3 -- No --> A4 --> A2
+  end
+
+  %% Right Column - Scheduling
+  subgraph B["📅 Scheduling"]
+    direction TB
+    B1["👩‍💻 Group by Topic"]
+    B2["📅 Schedule Talks"]
+    B3["📝 Send Confirmations"]
+    B4["📅 Add to Calendar"]
+    B5["📢 Share Schedule"]
+    B1 --> B2 --> B3 --> B4 --> B5
+  end
+
+  %% Flow between columns
+  A3 -- Yes --> B1
+
+  %% Styling
+  classDef default fill:#f0f7ff,stroke:#1976d2,stroke-width:3px,color:#0d47a1,padding:15px;
+  classDef process fill:#e3f2fd,stroke:#1976d2,stroke-width:3px,color:#0d47a1;
+  classDef decision fill:#fff8e1,stroke:#ff8f00,stroke-width:3px,color:#e65100;
+  class A,B process;
+  class A3 decision;
+```
+
+  </div>
+</details>
 
 - This should end at least six weeks before the event.
 - Start with a date and time TBA during proposal stage.
@@ -62,6 +139,47 @@ The function of the Lightning Talks Event is to allow opportunities for members
 
 #### Organizing talks
 
+<details>
+  <summary>🎤 View Speaker Preparation Process</summary>
+  <div style={{marginTop: '1rem'}}>
+
+```mermaid
+%%{init: {'theme':'base', 'themeVariables': {'fontSize':'24px', 'fontFamily':'arial'}}}%%
+flowchart LR
+  %% Left Column - Talk Preparation
+  subgraph A["🗂 Talk Preparation"]
+    direction TB
+    A1["🗂 Organize Talks"]
+    A2["✅ Send Checklists"]
+    A3{"Info Missing?"}
+    A4["📬 Request Info"]
+    A1 --> A2 --> A3
+    A3 -- Yes --> A4 --> A2
+  end
+
+  %% Right Column - Speaker Prep
+  subgraph B["👤 Speaker Prep"]
+    direction TB
+    B1["📸 Collect Speaker Info"]
+    B2["📁 Create Shared Folder"]
+    B3["✅ Verify Materials"]
+    B1 --> B2 --> B3
+  end
+
+  %% Flow between columns
+  A3 -- No --> B1
+
+  %% Styling
+  classDef default fill:#f5f5f5,stroke:#2e8555,stroke-width:3px,color:#1a1a1a,padding:15px;
+  classDef process fill:#e6f3ed,stroke:#2e8555,stroke-width:3px,color:#1a1a1a;
+  classDef decision fill:#fff8e1,stroke:#ff8f00,stroke-width:3px,color:#e65100;
+  class A,B process;
+  class A3 decision;
+```
+
+  </div>
+</details>
+
 - Create big issue cards for each coordinator with checklist, but smaller chunks on Project board more closely tied to time (ie, collect initial info (bio, headshot, socials), one week from date (title, description, slides)
   - All of information should be in one central document or folder.
     - Within that folder, there is a checklist that has each category (initial info checklist, talk checklist, etc.)
@@ -71,10 +189,48 @@ The function of the Lightning Talks Event is to allow opportunities for members
 
 ##### Week of
 
-- Send message to speaker channel with direction the week of - Let them know there’s a lag between the stream and the speaker - Ask them to mute or better yet, hide your youtube stream
+<details>
+  <summary>🎭 View Event Day Process</summary>
+  <div style={{marginTop: '1rem'}}>
+
+```mermaid
+%%{init: {'theme':'base', 'themeVariables': {'fontSize':'26px', 'fontFamily':'arial'}}}%%
+flowchart LR
+  %% Left Column - Pre-Event
+  subgraph A["📋 Pre-Event"]
+    direction TB
+    A1["🧾 Final Prep & Tech Check"]
+    A2["📨 Send Directions to Speakers"]
+    A3["🔗 Share Event Link"]
+    A4["⏰ Set Reminders"]
+    A1 --> A2 --> A3 --> A4
+  end
+
+  %% Right Column - Event
+  subgraph B["🎤 Event"]
+    direction TB
+    B1["🎬 Start Recording"]
+    B2["🧑‍🏫 Talks Begin"]
+    B3["❓ Q&A Session"]
+    B1 --> B2 --> B3
+  end
+
+  %% Flow between columns
+  A4 --> B1
+
+  %% Styling
+  classDef default fill:#f5f5f5,stroke:#2e8555,stroke-width:3px,color:#1a1a1a,padding:15px;
+  classDef process fill:#e6f3ed,stroke:#2e8555,stroke-width:3px,color:#1a1a1a;
+  class A,B process;
+```
+
+  </div>
+</details>
+
+- Send message to speaker channel with direction the week of - Let them know there's a lag between the stream and the speaker - Ask them to mute or better yet, hide your youtube stream
   (For ref: Bc there is a lag, if you’re watching and up next, you’ll be introduced before the next talk is over.)
 
-### Communication
+### Communication {#communication-section}
 
 #### For LT Team
 

docs/lunch-and-learns/process-docs.md

@@ -31,8 +31,6 @@ tags:
   - 'lunch and learns'
 ---
 
-Below is the entire lifecycle of a Virtual Coffee Lunch & Learn session.
-
 ## Roles
 
 There are several moving parts to making a successful Lunch & Learn. These docs are organized as to not assume one person is doing multiple roles (they could but they don't have to). It will also make it easy to assign roles as needed as our volunteer groups expand and contract.
@@ -73,6 +71,62 @@ Includes Editors and Graphics Coordinator (GC) who handle post-event cleanup of
 
 ## Scheduling a Lunch & Learn
 
+### Overview of the Scheduling Process
+
+Here's a visual overview of the scheduling workflow that will be explained in detail below:
+
+<details>
+  <summary>📊 View Workflow Diagram for Scheduling a Lunch & Learn</summary>
+  <div style={{marginTop: '1rem'}}>
+```mermaid
+%%{init: {'theme':'base', 'themeVariables': {'fontSize':'16px', 'fontFamily':'Arial'}}}%%
+flowchart LR
+  %% Left Column - Request Review
+  subgraph A["📬 Request Review"]
+    direction TB
+    A1["📅 Speaker submits request form"]
+    A2["📋 LC and DW review topic"]
+    A3["✅ Topic approved"]
+    A1 --> A2 --> A3
+  end
+
+%% Right Column - Scheduling Stage
+subgraph B["Scheduling 📅"]
+direction TB
+B1["LC checks calendar for dates 🗓"]
+B2["Confirm Host/Moderator 🗣️"]
+B3{"Time slots available?"}
+B4["Finalize date with Speaker"]
+B5["Add to Google Calendar"]
+B6["Send invites to team"]
+B7["Request more dates if needed"]
+
+    B1 --> B2 --> B3
+    B3 -->|Yes| B4
+    B3 -->|No| B7
+    B4 --> B5 --> B6
+
+end
+
+%% Connect the two subgraphs
+A3 --> B1
+
+%% Flow within Scheduling
+B1 --> B2 --> B3
+B3 -->|Yes| B4 --> B5 --> B6
+B3 -->|No| B7 --> B1
+
+%% Styling
+classDef default fill:#f5f5f5,stroke:#2e8555,stroke-width:2px,color:#333,padding:10px;
+classDef process fill:#e6f3ed,stroke:#2e8555,stroke-width:2px,color:#333;
+class A,B process;
+
+```
+</div>
+</details>
+
+## Detailed Scheduling Process
+
 ### Lunch & Learn Session Request Is Submitted
 
 - **KICK-OFF ACTION:** The Speaker fills out a Lunch & Learn request form.
@@ -83,7 +137,11 @@ Includes Editors and Graphics Coordinator (GC) who handle post-event cleanup of
 
 - The LC and DW receive the form submission.
 
-#### Scheduling Workflow
+### Scheduling Workflow
+
+Once a request is received, the following workflow is initiated to schedule the Lunch & Learn session. This section provides the detailed steps that follow the overview shown above.
+
+Here's the step-by-step process for scheduling a Lunch & Learn session:
 
 1. The LC checks the calendar for availability in order of the Speaker's preferred dates.
 
@@ -164,3 +222,4 @@ _**NOTE:** The Moderator and the Host can be the same person._
   - The VC events page
   - X
   - The newsletter team (if the relevant issue has not yet been published)
+```

docs/monthly-challenges/facilitators-docs/facilitate-a-challenge.md

@@ -37,6 +37,80 @@ Let us know your availability for the challenge in the reminder thread that drop
 
 If you have ideas for a new challenge(s), you can propose and discuss them in the `#vc-monthly-challenge-team` channel on Slack or open a new [discussion on GitHub](https://github.com/Virtual-Coffee/VC-Community-Docs/discussions).
 
+Below are diagrams of the Monthly Challenge workflow. Click to expand each section to view the detailed workflow.
+
+<details>
+  <summary>📊 View Workflow Diagrams</summary>
+  <div style={{marginTop: '1rem'}}>
+
+#### Planning + Promoting
+
+```mermaid
+%%{init: {'theme':'base', 'themeVariables': {'fontSize':'24px', 'fontFamily':'arial'}}}%%
+flowchart LR
+  %% Left Column - Planning
+  subgraph A["🛠 Planning"]
+    direction TB
+    A1["📢 Team leads receive ideas from members"]
+    A2["👥 Team leads pick an idea"]
+    A3["☕ Team leads and Coffee Table Group hosts discuss challenge details"]
+    A1 --> A2 --> A3
+  end
+
+  %% Right Column - Promoting
+  subgraph B["📬 Promoting"]
+    direction TB
+    B1["💬 Update #monthly-challenge channel topic a week before launch"]
+    B2["📣 Publish post about the challenge on VC's blog"]
+    B3["🧾 Post challenge announcement in #monthly-challenge Slack channel"]
+    B4["👩‍💻 Crosspost announcement to other community channels"]
+    B1 --> B2 --> B3 --> B4
+  end
+
+  %% Flow between columns
+  A3 --> B1
+
+  %% Styling
+  classDef default fill:#f5f5f5,stroke:#2e8555,stroke-width:3px,color:#1a1a1a,padding:15px;
+  classDef process fill:#e6f3ed,stroke:#2e8555,stroke-width:3px,color:#1a1a1a;
+  class A,B process;
+```
+
+#### Check-Ins + Post-Challenge
+
+```mermaid
+%%{init: {'theme':'base', 'themeVariables': {'fontSize':'23px', 'fontFamily':'arial'}}}%%
+flowchart LR
+  %% Left Column - Check-Ins
+  subgraph A["🧭 Check-ins"]
+    direction TB
+    A1["🗂 Participants set personal goals Mondays at 10 AM"]
+    A2["✅ Post thread for async progress updates"]
+    A3["🤖 Automate check-ins for certain challenges"]
+    A1 --> A2 --> A3
+  end
+
+  %% Right Column - Post-Challenge
+  subgraph B["🌟 Post-Challenge"]
+    direction TB
+    B1["🗒️ Collect feedback and takeaways from participants"]
+    B2["📰 Publish challenge recap in newsletter or blog"]
+    B3["🔄 Plan improvements for future challenges"]
+    B1 --> B2 --> B3
+  end
+
+  %% Flow between stages
+  A3 --> B1
+
+  %% Styling
+  classDef default fill:#f5f5f5,stroke:#2e8555,stroke-width:3px,color:#1a1a1a,padding:15px;
+  classDef process fill:#e6f3ed,stroke:#2e8555,stroke-width:3px,color:#1a1a1a;
+  class A,B process;
+```
+
+  </div>
+</details>
+
 ## Before the Challenge
 
 ### Coordinating with the Coffee Table Groups
@@ -105,7 +179,6 @@ Some challenges require daily check-in. You can automate it using the Slack bot.
 
 - Provide feedback in the `#vc-monthly-challenge-team` channel, like what went well and what could've gone better for the challenge. Let us know what support you need and what things you think would be nice to do next time.
 - Update the README file in the challenge's folder with:
-
   - new script templates and things we did for the challenge,
   - the month and year of the challenge,
   - the blog post(s) for the challenge, if any.