From 24fedaef724a1cae3ba8919795c5e7e31d29c2be Mon Sep 17 00:00:00 2001 From: Nanda128 Date: Mon, 19 May 2025 02:14:48 +0100 Subject: [PATCH] handovers: Oopsie daisie with the triple backtick markdown --- Committee/2024-2025/Handovers/PRO.md | 24 ++++++++++-------------- 1 file changed, 10 insertions(+), 14 deletions(-) diff --git a/Committee/2024-2025/Handovers/PRO.md b/Committee/2024-2025/Handovers/PRO.md index b733480..d75c40c 100644 --- a/Committee/2024-2025/Handovers/PRO.md +++ b/Committee/2024-2025/Handovers/PRO.md @@ -34,7 +34,7 @@ Trying to do everything yourself is a recipe for burnout. - For each upcoming event, you need to navigate to https://cp.ulwolves.ie/manage/events/add and fill out the form. - For the "Description" section, you can copy and paste the email or discord announcement (removing things like the " - ```@everyone```" tag). + ``@everyone``" tag). - Every event needs to be bookable, so click on the "Book on UL Wolves" radio button in the "Pre-Booking" section. You don't need tickets (unless its big events like PyCon) or booking notifications. - Leave all settings as default with respect to bookings, unless otherwise specified. @@ -51,15 +51,14 @@ Trying to do everything yourself is a recipe for burnout. - The society usually conducts most communication and activity on Discord, so you should try to point people to https://discord.skynet.ie as much as you can. Especially in the beginning of the year. - Every announcement begins life as a thread in the "pro-forum" channel in the Committee Discord. You'll need to create - a new post on the forum with the format as follows: ```YYYY-MM-DD {Event Name} Comms``` with the date referring to the + a new post on the forum with the format as follows: ``YYYY-MM-DD {Event Name} Comms`` with the date referring to the date of the event. - For example, if the event is a capture the flag on the 1st of October, the post should be titled - ```2025-10-01 CTF Comms```. + ``2025-10-01 CTF Comms``. - In the thread, you want to link to the committee forum thread in the first post and any important information you might need to make an announcement off of. -- Start making a base announcement, there isn't a specific format but usually ours followed something like this: +- Start making a base announcement, there isn't a specific format, but usually ours followed something like this: -``` Hey everyone/@everyone, {Quip about the event} @@ -71,8 +70,7 @@ See you then! Book your slot on Wolves: {Wolves Link} -[Any other important links] [P.S. Do not use embeds, have the links out there. People wouldn't feel secure clicking on a random link they cant see at first glance in an email] -``` +{Any other important links} [P.S. Do not use embeds, have the links out there. People wouldn't feel secure clicking on a random link they cant see at first glance in an email] - Ideally you want to include more than just the base format, you don't want things getting too same-y - After making the announcement, put it in the pro-forum thread and wrap it in triple backticks to make it a code block. @@ -152,15 +150,14 @@ Book your slot on Wolves: {Wolves Link} - For the "Lead" section, try to use the forgejo handle of the person who organized the event. - You can use the following template: -``` # {Event Name} -| Date | {Date} | -|----------|----------------| -| Location | {Location} | +| Date | {Date} | +|----------|---------------------------| +| Location | {Location} | | Time | {Start Time} - {End Time} | -| Type | {Type} | -| Lead | {Lead} | +| Type | {Type} | +| Lead | {Lead} | ## Overview @@ -182,7 +179,6 @@ Book your slot on Wolves: {Wolves Link} ### Poster ![Poster]({Poster Link}) -``` - Upload any posters to the same directory as the event file, and link to them in the "Poster" section. - Copy the same filename as the Markdown file, and rename the poster to it.