Contributing Events to triad.build!

Welcome! Contributing events to triad.build is easy and accessible. By contributing events to triad.build you help to ensure that the events you or your org host are accessible to the wider Triad community outside of Lex and Instagram, you're able to make your events posted on triad.build look exactly how you want, and ensure that events posted are as up-to-date and accurate as possible. This project's maintainers hope you'll join them in trying to help foster a greater and more integrated queer community in Greensboro and greater Triad Area.

There are a couple different ways to contribute events to the calendar, but the main way that'll be gone over in this guide will be by using Google Calendar. If you have your events hosted via another service or software package online feel free to email this project's maintainers at leileixiawork@gmail.com to discuss integrating those to minimize your work required.

Publishing Google Calendar events

Follow the steps below to make your Google Calendar public, then submit it using the form above.

• Create a Google Account for your events if one doesn't already exist. The email address associated with the google calendar you publish may be visible in some cases, so, ensure it's not an email you use for your personal life.
• Go to to calendar.google.com and navigate to the menu on the left side of your screen that says "My calendars" and "Other calendars". If you don't already have a calendar that's ready for public display, press the + symbol, and then click "Create new calendar".
• 
• You should then be presented with a screen that looks like the following. Fill out the information and click "Create calendar". After it's created it'll be availabe on the left side of your screen under "My calendars"
• 
• When your calendar is created, access it's "Settings and sharing" menu accessible on desktop by hovering over it with your mouse and clicking the three dots which appear, then "Settings and sharing"
• 
• When you're in your Calendar settings, navigate to "Access permissions for events" and tick the checkbox that says "Make available to public", and ensure "See all event details" is selected in the menu to the right of the checkbox.
• 
• Now scroll down to the bottom of the page to the "Integrate calendar" section. The Calendar ID ought to be featured here like in the image below, and should end in @group.calendar.google.com (in some cases it will be your email, if you feel comfortable with that you can share it but if you don't you'll have to follow the previous steps to create a new calendar). This Calendar ID is what you need to send to this project's maintainers either via our calendar submission form, an email, a github pull request, or just text one of this project's maintainers if you know their number ❤
• 

Formatting Tips

• When adding events to the calendar, ensure that your events are being added to the correct calendar
👍
• When adding events to the calendar, ensure that your events are being assigned a time period, and that it's under 24 hours. Events longer than 24 hours or for an entire day simply will not appear on triad.build
👎
👎
👍
• When adding events to the calendar, try not to leave the location field blank. Try and fill it with either a location that will appear and be google maps compatible, or feel free to set an arbitrary location.
👎
👍
👍
👍

• When adding events to the calendar, try not to leave the description blank. Even if you don't feel like adding much information, like if for example you're throwing something on real quick, atleast try and link to where you can find more information for the event (website or social media account). For bonus points, feel free to include an image or poster you've made for your event (guide on how to do this is detailed below)
👎
👍
👍

triad.build Calendar Preferred Guidelines and Reccomendations

• triad.build has a "badge" system for events, think of them like a :twitter: on the entity formerly known as Twitter. Badges are placed at the beginning of an event's title to help provide users on triad.build the ability to find a group's events or a genre of event at a glance. Some examples of badges are :test:, :triad:, :fojrp:, :dykes_on_bikes:, :coalition_theater:, and :hackrva:. When you submit an event on your calendar, they'll be added at the beginning of the titles of events for your group.
• It's reccomended to only use a combination of no more than two badges+emotes in combination, so if your group already has a custom badge then please only insert up to one emoji in the title of your events
• Valid and Invalid Title Examples:
👍 Greensboro Community Clothes Swap
👍 :triad: Greensboro Queer Clothes Swap
👍 :triad: 👗 Greensboro Queer Clothes Swap
👍 :triad: 👕 Greensboro Queer Clothes Swap
👍 👗 Greensboro Community Clothes Swap
👍 👗👕 Greensboro Community Clothes Swap
👎 :triad:👗👕 Greensboro Queer Clothes Swap
👎 :triad:👖👗👕 Greensboro Queer Clothes Swap
👎 👖👗👕 Greensboro Community Clothes Swap

• Badges are by default added automatically to your events, but they can be added manually by you in the titles of your events. If you're curious about what options are available, feel free to reach out to the maintainers of this project.
• triad.build has a system for showing images in the preview modals when an event is clicked on. The first three direct links to images hosted online will be displayed at the head of the event preview modals. This only applies to events hosted on Google Calendar, events grabbed from other sources will in the future include their fetched image in the preview modal automaticaly.
• Example of this being used on an event's modal:

• The easiest option is to use imgur like in the tutorial below, but if you run your own website you can directly link to images hosted there
• If you want to implement it yourself, you can follow these steps using imgur
• Navigate to catbox.moe and drag and drop your image there (optionally you could log in, and in that way you will have access to the photo later or delete it. If you just upload without log in, you can never delete that picture), uploading the images when prompted.
• After your image is uploaded, click the link underneath the file name. Ensure the link features ".png", ".jpg", or ",jpeg" at the end of it's url. An example of what this url would look like is https://files.catbox.moe/89uz3p.png. If your URL doesn't include this file type on the end then it won't properly render inside triad.build
• Inside the description for your event, include your image URL as either a link or in plaintext. If all went well your image will successfully render on triad.build
• If your group has consistent events at the same time every week, it's okay to put those events on the calendar as a repeating event. There's multiple groups which do weekly events but aren't able to update the calendar every week because of the labor and relative decentralization of their groups, and that's okay, as long as there's some kind of indication that an event *may* be occuring it's still cool as hell and I appreciate it.
• The standards above, embedding proper location data and time data, as well as a description with enough information to atleast find the event's information elsewhere on the internet, will help ensure that you get the engagement out of having your events on triad.build that you may desire. They're not necessary, and you'll probably see other calendars which don't follow these standards whatsoever, but I also really appreciate it when you follow these standards.