USRSE / USRSE/usrse.github.io

Change titles/text on repeating community call events so they don't look like duplicates

Open
#898 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

design discussion-needed
Dominant language
HTML
Stars
33
Forks
104
Avg merge
12h 3m
Merged PRs (30d)
10

Description

In #833 @jdamerow and @christophernhill added a repeating event, fixing the calendar so we have community calls alternate Thursdays and Fridays

This works as intended but @cmaimone @exoticDFT noticed that it can look like there are duplicate events, e.g. in this build artifact: https://output.circle-artifacts.com/output/job/65559ca9-11aa-496c-bba3-a9f0279ba5f3/artifacts/0/usrse.github.io/events/index.html

This is true on the live page as of posting this issue (https://us-rse.org/events/) but if you click on them you can see one is the June call on a Friday and the other is July on Thursday.

One solution might be to changed the title / text on the two repeating events so they didn't appear to be repeating.
For example, we could change the title of the original event to be "Bimonthly Community Call on Thursday" and the title of the one that was added to "Bimonthly on Friday" or something like that.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the generated events/index.html artifact and compare the two alternating community call entries shown there. Locate the source event definitions that produce those entries, update their titles or text so the Thursday and Friday calls are distinguishable, then verify the events page no longer makes them look like duplicates.

Written by the indexing model from the issue text.

Assessment

Tech stack
html
Domain
content, web-dev
Issue type
Bug
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.