Fix Toronto footer Call for Speakers link to use city-specific Tally URL#128
Conversation
update new version for 2026
adjust sponsors layout
switch section and add logo links
adjust schedule
update sponsor logo
add community partner
Update schedule, sponsors, map, speakers
Update schedule, speaker and change nav bar
update schedule and add sponsor
update sponsor
update content
|
Hello team, Switching the "Call for Speakers" link to the external Tally form is excellent and solves the registration issue, but it has created an operational workflow gap that we need to address immediately. The "Our Speakers" section on our main site (currently showing test speakers) remains a static section within the code. Now that the speaker recruitment process has moved to Tally, we need to define a manual (or automated) process to transfer information of approved speakers from Tally to the site code. Otherwise, we will approve speakers in Tally, but the main site will never be updated, and the new Toronto 2026 speakers will not be visible on the site. I suggest that as soon as speakers are finally approved in Tally, a ticket should be opened for the development team to update their information (photo, bio, LinkedIn) in the static site files. @bibschan , and @vincent6767 please take this into account for the final process. |
|
@ahmad1368 thanks for your two cents! Sometimes a speaker is confirmed but we don't yet want to announce on the website, we typically wait to confirm a few then we batch update it manually. In this case, automations won't work for our use case. Does this make sense? happy to ping the team when we're ready to push out info on speakers |
Sounds good to me. Whenever the speaker details are finalized and shared with us, I’m fully ready to update the website code with their information (photo, bio, LinkedIn, etc.). Just ping me when the batch is ready and I’ll take care of it. |
|
ok great -- let me know if there are any blockers at this time to get this PR merged :) |
Everything looks great code-wise! The only minor thing is our workflow: we need to merge this into staging first instead of main. I've already messaged Vincent on LinkedIn to switch the base branch to staging. Once he updates it, we are good to merge. No other blockers! |
|
@ahmad1368 Thanks for reminding me about the workflow. I have just changed the PR to target the staging branch. Please review and merge it afterwards. |
4 participants
Request from @bibschan
Fix the Toronto footer “Call for Speakers” link so it uses the city-specific Tally URL instead of the default Vancouver /our-speakers/ fallback. Verified by switching the site to Toronto and confirming the footer “Call for Speakers” link updates to https://tally.so/r/rjBeN5.
Please review and approve @nichanunpong @ahmad1368
P.S. I used Copilot to help fix the issue.