publicity/showcase: improve formatting and readability in Publicity and Showcases documents
This commit is contained in:
parent
ba8b364d65
commit
9a03ce048d
2 changed files with 43 additions and 47 deletions
|
@ -1,21 +1,20 @@
|
|||
## Publicity
|
||||
Over the course of the year, we ran a total of 25 events, all listed on wolves and announced on Discord.
|
||||
Over the course of the year, we ran a total of 25 events, all listed on wolves and announced on Discord.
|
||||
|
||||
We ran regular weekly activities on Wednesday,
|
||||
using our Discord Server and emails to inform our members of upcoming events and opportunities.
|
||||
Our Discord server was our social hub of communication between members and committee
|
||||
and has now grown to have ~300 members.
|
||||
We ran regular weekly activities on Wednesday, using our Discord Server and emails to inform our members of upcoming events and opportunities.
|
||||
Our Discord server was our social hub of communication between members and committee
|
||||
and has now grown to have ~300 members.
|
||||
|
||||
We also collaborated a lot with other societies, which helped bring a lot of new eyes to us and to what we do.
|
||||
We also collaborated a lot with other societies, which helped bring a lot of new eyes to us and to what we do.
|
||||
|
||||
We used posters for larger events, since we began putting more effort and quality into the creation of our posters.
|
||||
This helped create a more professional image for our society and helped us stand out from other societies.
|
||||
We used posters for larger events, since we began putting more effort and quality into the creation of our posters.
|
||||
This helped create a more professional image for our society and helped us stand out from other societies.
|
||||
|
||||
### Other Societies
|
||||
|
||||
We worked with several Societies over the last year
|
||||
which has meant more advertising for our society in addition to helping other societies grow.
|
||||
This includes collaborations and larger-scale events like our Birthday event, SISTEM, and our Unity Workshop.
|
||||
We worked with several Societies over the last year
|
||||
which has meant more advertising for our society in addition to helping other societies grow.
|
||||
This includes collaborations and larger-scale events like our Birthday event, SISTEM, and our Unity Workshop.
|
||||
|
||||

|
||||

|
||||
|
@ -23,23 +22,21 @@ This includes collaborations and larger-scale events like our Birthday event, SI
|
|||
|
||||
### Posters
|
||||
|
||||
This year included a shift in our approach to posters.
|
||||
We decided to put more effort and quality into the creation of our posters,
|
||||
which also made them difficult to create for weekly events.
|
||||
Thus,
|
||||
we could ensure that our larger events had more powerful visuals
|
||||
and helped communicate to our members that this event is more significant than our weekly events.
|
||||
This year included a shift in our approach to posters.
|
||||
We decided to put more effort and quality into the creation of our posters, which also made them difficult to create for weekly events.
|
||||
Thus, we could ensure that our larger events had more powerful visuals
|
||||
and helped communicate to our members that this event is more significant than our weekly events.
|
||||
|
||||
Posters can be found [on our forgejo][0]
|
||||
Posters can be found [on our forgejo][0]
|
||||
|
||||
### Event Announcements
|
||||
|
||||
We primarily used Discord and Emails for our event announcements,
|
||||
while prompting our users to sign up for events on Wolves.
|
||||
This helped us keep track of who was attending our events and allowed us to send out reminders to our members.
|
||||
Our Discord server also allowed us to quickly issue reminders or updates to our members, which greatly improved our communication.
|
||||
We primarily used Discord and Emails for our event announcements,
|
||||
while prompting our users to sign up for events on Wolves.
|
||||
This helped us keep track of who was attending our events and allowed us to send out reminders to our members.
|
||||
Our Discord server also allowed us to quickly issue reminders or updates to our members, which greatly improved our communication.
|
||||
|
||||
Event Announcements can be found [on our forgejo][1]
|
||||
Event Announcements can be found [on our forgejo][1]
|
||||
|
||||
[0]: https://forgejo.skynet.ie/Computer_Society/open-goverance/src/branch/main/Events/2024-2025/Posters
|
||||
[1]: https://forgejo.skynet.ie/Computer_Society/open-goverance/src/branch/main/Events/2024-2025
|
||||
|
|
|
@ -4,36 +4,35 @@
|
|||
|
||||
To prove trip attendance, please see <<https://cp.ulwolves.ie/manage/events/16284>>
|
||||
|
||||
This was a trip made by UL Computer Society to PyCon Ireland 2024,
|
||||
This was a trip made by UL Computer Society to PyCon Ireland 2024,
|
||||
hosted in the Radisson Blu Hotel in Dublin on November 16th-November 17th, 2024.
|
||||
This section will cover the organization of the trip.
|
||||
|
||||
Since we had to find transportation for this trip, preparation for this event took a lot of organization.
|
||||
Thankfully, we had lots of information from previous years to help us with this.
|
||||
We arranged transport for all members to and from Dublin & Limerick, and their event tickets.
|
||||
The cost for both transport and tickets was subsidized from us,
|
||||
making attendance to the event much cheaper for our members.
|
||||
We used interest checks and surveys to gauge how many members were interested in attending the event, using that information to know how many tickets we needed to buy.
|
||||
We were also able to negotiate a group discount for the tickets, which helped us save money.
|
||||
Once we had the numbers regarding who were planning on attending,
|
||||
we booked the tickets for the events and the buses from Limerick to Dublin and back.
|
||||
Things went smoothly, and we were able to adhere to our initial itinerary.
|
||||
We didn't have to rush coming back to Limerick, since we gave ourselves plenty of time to get back.
|
||||
This gave us more time for things like unplanned bathroom breaks.
|
||||
Since we had to find transportation for this trip, preparation for this event took a lot of organization.
|
||||
Thankfully, we had lots of information from previous years to help us with this.
|
||||
We arranged transport for all members to and from Dublin & Limerick, and their event tickets.
|
||||
The cost for both transport and tickets was subsidized from us, making attendance to the event much cheaper for our members.
|
||||
We used interest checks and surveys to gauge how many members were interested in attending the event, using that information to know how many tickets we needed to buy.
|
||||
We were also able to negotiate a group discount for the tickets, which helped us save money.
|
||||
Once we had the numbers regarding who were planning on attending,
|
||||
we booked the tickets for the events and the buses from Limerick to Dublin and back.
|
||||
Things went smoothly, and we were able to adhere to our initial itinerary.
|
||||
We didn't have to rush coming back to Limerick, since we gave ourselves plenty of time to get back.
|
||||
This gave us more time for things like unplanned bathroom breaks.
|
||||
|
||||
### SISTEM
|
||||
|
||||
In Semester 2 of this year we helped run an event called SISTEM,
|
||||
the Student Inter-Society Technology and Enterprise Meetup.
|
||||
This was a large event that happened in the Kemmy Business School on March 29th, 2025.
|
||||
Usually, this event is run by multiple societies, across multiple universities in Ireland.
|
||||
It is the largest event of its kind in Ireland, an entirely-student run event.
|
||||
In Semester 2 of this year we helped run an event called SISTEM,
|
||||
the Student Inter-Society Technology and Enterprise Meetup.
|
||||
This was a large event that happened in the Kemmy Business School on March 29th, 2025.
|
||||
Usually, this event is run by multiple societies, across multiple universities in Ireland.
|
||||
It is the largest event of its kind in Ireland, an entirely-student run event.
|
||||
|
||||
We had 30-40 people attending, across multiple universities, like UL, UCC, and UCD.
|
||||
The event also gathered sponsorship from LERO, and assistance from Google.
|
||||
We had 30–40 people attending, across multiple universities, like UL, UCC, and UCD.
|
||||
The event also gathered sponsorship from LERO, and assistance from Google.
|
||||
|
||||
In addition to the sponsorship and assistance, we also had industry speakers from companies like Google, and LERO at the event.
|
||||
They would give talks about specific topics they're currently working on, with plenty of time for questions and answers.
|
||||
In addition to the sponsorship and assistance, we also had industry speakers from companies like Google, and LERO at the event.
|
||||
They would give talks about specific topics they're currently working on, with plenty of time for questions and answers.
|
||||
|
||||
One of the more impressive events that UL Computer Society was able to run this year,
|
||||
we were able to hit the record for the number of pizzas ordered for an event in UL history.
|
||||
One of the more impressive events that UL Computer Society was able to run this year,
|
||||
we were able to hit the record for the number of pizzas ordered for an event in UL history.
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue