PythonIreland / PythonIreland/2026.pycon.ie

Confirm ticket pricing tiers before making them public

Open
#115 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

content question
Dominant language
HTML
Stars
1
Forks
0
Avg merge
10m
Merged PRs (30d)
1

Description

Context

PR #111 added visible prose on the homepage and a new key-questions.html partial that display the ticket price range using the values from hugo.toml:

  • Student: €40
  • Early Bird: €70
  • General: €100
  • Corporate: €300

These values are currently shown on the homepage as: "Tickets from €40 to €300" and in the Q&A section: "Tickets range from €40 (student) to €300 (corporate)."

They are also referenced in the Event schema AggregateOffer (lowPrice / highPrice).

Problem

The ticket pricing has not been officially confirmed or announced. Publishing these figures before the team agrees on them could be misleading to attendees and sponsors.

Questions to resolve

  • Are the current price tiers (€40 / €70 / €100 / €300) confirmed for 2026?
  • When will ticket sales open (needed to update ticketsUrl in hugo.toml and switch AggregateOffer.availability from PreOrder to InStock)?
  • Should the prices be hidden from the homepage until sales open, or is showing them now acceptable?

Options

  1. Confirm prices as-is — merge PR #111 as-is once prices are agreed
  2. Hide prices until sales open — comment out the ticket price display in key-questions.html and the key-facts bar until Tito/ticketing is set up
  3. Show placeholder wording — replace "€40 to €300" with "TBA" or "from €X" once a minimum price is confirmed

Contributor guide

No contributing guide indexed for this repository

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

Review PR #111, hugo.toml, key-questions.html, the homepage key-facts bar, and the Event schema AggregateOffer. First confirm the team's decision on the 2026 tiers, sales timing, and whether prices should be public; done means the selected option is consistently reflected in those locations.

Written by the indexing model from the issue text.

Assessment

Tech stack
html, hugo
Domain
content, web-dev
Issue type
Documentation
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.