PythonIreland / PythonIreland/2026.pycon.ie
Confirm ticket pricing tiers before making them public
Nobody has claimed this yet.
- 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
ticketsUrlin hugo.toml and switchAggregateOffer.availabilityfromPreOrdertoInStock)? - Should the prices be hidden from the homepage until sales open, or is showing them now acceptable?
Options
- Confirm prices as-is — merge PR #111 as-is once prices are agreed
- Hide prices until sales open — comment out the ticket price display in
key-questions.htmland the key-facts bar until Tito/ticketing is set up - 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
- 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.
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