Skip to content

Commit 861e5a8

Browse files
authored
Merge pull request #643 from TimOsahenru/cleanup-for-conferences.py-file
Cleanup for conferences.py file
2 parents e47cd14 + 28edf6e commit 861e5a8

File tree

9 files changed

+81
-246
lines changed

9 files changed

+81
-246
lines changed

.github/ISSUE_TEMPLATE/add_conference.yml

Lines changed: 0 additions & 95 deletions
This file was deleted.

.github/workflows/conference.yml

Lines changed: 0 additions & 56 deletions
This file was deleted.

.github/workflows/conference_auto_respond.yml

Lines changed: 0 additions & 44 deletions
This file was deleted.

CONTRIBUTING.md

Lines changed: 39 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -166,3 +166,42 @@ The diagram below explains how information is generated for the about page, show
166166
![Git push terminal](/assets/images/git_push_terminal.png)
167167

168168
- Once you’ve committed and pushed all of your changes to GitHub, go to the page for your fork on GitHub, select your development branch, and click the pull request button. Please ensure that you compare your feature branch to the desired branch of the repo you are supposed to make a PR to. If you need to make any adjustments to your pull request, just push the updates to GitHub. Your pull request will automatically track the changes in your development branch and update it. 🥳
169+
170+
## Creating an event
171+
172+
Events are currently created manually by adding entries to `_data/events.json`. To create a conference, use the following JSON structure:
173+
174+
```
175+
{
176+
"name": "Conference name",
177+
"url": "https://blackpythondevs.com/",
178+
"start_date": "2025-02-10",
179+
"end_date": "2025-09-20",
180+
"location": "Thailand",
181+
"description": "Lorem ipsum dolor sit amet consectetur adipiscing elit ...",
182+
"speaker": "Tim Osahenru"
183+
}
184+
```
185+
186+
### Regular meetups
187+
188+
We have two recurring meetups: **Coffee and Code** and our **Monthly Meetup**. These events remain consistent in format, with only the **date, time, and speaker** subject to change. Updates can be made within the `meetups` list:
189+
190+
```
191+
{
192+
"name": "Coffee and Code",
193+
"date": "2023-09-20",
194+
"location": "Online (Discord)",
195+
"description": "A casual meetup for developers to code together.",
196+
"speaker": "Jay Miller",
197+
"topic": "Web Development"
198+
},
199+
{
200+
"name": "Monthly meetup",
201+
"date": "2023-09-20",
202+
"location": "Remote",
203+
"description": "Share ideas, and network over coffee.",
204+
"speaker": "Jay Miller",
205+
"topic": "Open Source"
206+
}
207+
```

_data/conferences.json

Lines changed: 0 additions & 12 deletions
This file was deleted.

_data/events.json

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,5 @@
1+
{
2+
"meetups": [],
3+
"conferences": [],
4+
"partners": []
5+
}

_includes/conferences.html

Lines changed: 8 additions & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -1,25 +1,20 @@
1-
{% if site.data.conferences.size > 0 %}
1+
{% if site.data.events.conferences.size > 0 %}
22
<div class="conference grid">
3-
{% for conference in site.data.conferences %}
3+
{% for conference in site.data.events.conferences %}
44
<article>
55
<h2>
6-
<a href="{{ conference.url }}">{{ conference.conference_name }}</a>
6+
<a href="{{ conference.url }}">{{ conference.name }}</a>
77
</h2>
8+
<h5>{{ conference.speaker }}</h5>
89
<p>
9-
<strong>{{ conference.conference_start_date }} - {{ conference.conference_end_date }}</strong>
10+
<strong>{{ conference.start_date }} - {{ conference.end_date }}</strong>
1011
{% if conference.conference_location != "_No response_" %}
1112
<br />
12-
<strong>{{ conference.conference_location }}</strong>
13+
<strong>{{ conference.location }}</strong>
1314
</p>
1415
{% endif %}
15-
<p>Type: {{ conference.conference_type }}</p>
16-
{% if conference.summary != "_No response_" %}
17-
{{ conference.summary | markdownify }}
18-
{% endif %}
19-
{% if conference.speaking %}
20-
<h3>Speaking:</h3>
21-
{{ conference.speaking | markdownify }}
22-
{% endif %}
16+
<p>{{ conference.description }}</p>
17+
2318
</article>
2419
{% endfor %}
2520
</div>
@@ -28,4 +23,3 @@ <h3>Speaking:</h3>
2823
{% endif %}
2924

3025
<hr />
31-
<p>Have a Conference to Add - <a href="https://github.com/BlackPythonDevs/blackpythondevs.github.io/issues/new?assignees=&labels=conference&projects=&template=add_conference.yml&title=%5BCONFERENCE%5D+%3CCONFERENCE+NAME%3E+YYYY">Submit an Issue</a></p>

_includes/meetups.html

Lines changed: 23 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,23 @@
1+
{% if site.data.events.meetups.size > 0 %}
2+
<div class="conference grid">
3+
{% for meetup in site.data.events.meetups %}
4+
<article>
5+
<h2>
6+
<a href="https://discord.gg/XUc3tFqCT3">{{ meetup.name }}</a>
7+
</h2>
8+
<h5>Speaking: {{ meetup.speaker }}</h5>
9+
<p>
10+
<strong>{{ meetup.date }}</strong><br />
11+
<strong>{{ meetup.location }}</strong>
12+
</p>
13+
<p>{{ meetup.description }}</p>
14+
15+
<p>{{ conference.topic }}</p>
16+
</article>
17+
{% endfor %}
18+
</div>
19+
{% else %}
20+
<b>No Meetups</b>
21+
{% endif %}
22+
23+
<hr />

events.md

Lines changed: 6 additions & 25 deletions
Original file line numberDiff line numberDiff line change
@@ -4,36 +4,17 @@ lang: en
44
title: Events
55
---
66

7-
# Black Python Devs Events
8-
9-
## Coffee and Code
10-
11-
Join us every Friday for a cup of coffee and a chance to code with fellow Python enthusiasts. Our community is open to all levels of experience, from beginners to experts.
12-
13-
We’ll be discussing the latest trends in Python development, sharing tips and tricks, and working on projects together. Whether you’re looking to learn something new or just want to hang out with like-minded people, this is the perfect opportunity to do so. We look forward to seeing you there!
14-
157
# Upcoming Conferences
168

179
Black Python Devs aims to partner with Python conferences around the world to increase the visibility and opportunities for Black leadership in the Python community. We understand that when you put qualified individuals on stage and at conferences it increases their value and opportunities for employment.
1810

19-
<!--
20-
To add a conference one of the following should apply
21-
22-
1. A Black Python Dev Member should be speaking at the conference
23-
2. The conference should have programs in place to empower Black and other Historically Excluded Communities to contribute.
24-
25-
Sample
26-
-----
27-
28-
## CONFERENCE NAME (DATES), City, Region, Country
11+
Here are some highlighted upcoming conferences where you can find Black Python Developers involved on stage or behind the scenes
2912

30-
ONE SENTENCE DESCRIPTION OF THE CONFERENCE. Be sure to link to the conference itself.
13+
{% include conferences.html %}
3114

32-
### Speaking
33-
- PERSON - TALK or ROLE NAME
34-
---
35-
-->
15+
## Regular Meetups
3616

37-
Here are some highlighted upcoming conferences where you can find Black Python Developers involved on stage or behind the scenes
17+
Join us every Friday for a cup of coffee and a chance to code with fellow Python enthusiasts. Our community is open to all levels of experience, from beginners to experts.
3818

39-
{% include conferences.html %}
19+
We’ll be discussing the latest trends in Python development, sharing tips and tricks, and working on projects together. Whether you’re looking to learn something new or just want to hang out with like-minded people, this is the perfect opportunity to do so. We look forward to seeing you there!
20+
{% include meetups.html %}

0 commit comments

Comments
 (0)