Discontinued conferences
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 38/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- css
- Domain
- frontend
Research direction
No file or test is named. Start by locating the page or template that renders the events list and its associated stylesheet, then review how discontinued events are currently represented. Done means discontinued or inactive events have their own section and active events are easier to scan.
Written by the indexing model from the issue text.
Description
Would it make sense to lump discontinued events into its own section?
It feels like we have a pretty big list of discontinued events and events that haven't returned for 2 to 3 years, and it's a lot to visually process to find active events.
- Dominant language
- CSS
- Stars
- 20
- Forks
- 51
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from PyCon/pycon.org
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
-
Update social links Open
Difficulty 2/5 1-3 hours Newbie friendliness 35/100
Similar issues
-
S: triage
Difficulty 1/5 Under an hour Newbie friendliness 85/100
-
feature:Languages/Translations good first issue ready Web
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
digitalfabrik/integreat-app#4394 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
comp/desktop P3 type/bug
Difficulty 1/5 Under an hour Newbie friendliness 92/100
NousResearch/hermes-agent#118866 ·
-
bug
Difficulty 1/5 Under an hour Newbie friendliness 90/100
apache/cloudstack#14222 ·