fix: Match event name header typography across dashboards (#1368)

[Eshaan-byte]

Description

Changed event name header from <h1> to <h2> in Tickets and Common dashboards to match the Talk Dashboard typography for visual consistency across the unified platform.

Changes

• Updated pretixcontrol/event/index.html (Tickets Dashboard)
• Updated eventyay_common/event/index.html (Common Dashboard)

Result

All three dashboards now use consistent typography for event name headers:

• Font size: 1.75rem (h2)
• Font weight: 500
• Line height: 1.2

Testing

• Verified Tickets Dashboard displays event name with h2 styling
• Verified Common Dashboard displays event name with h2 styling
• Confirmed consistency with Talk Dashboard

Fixes #1368

Summary by Sourcery

Align event name header typography across dashboards by standardizing the heading level.

Enhancements:

• Change event name headers from h1 to h2 on the Tickets dashboard for consistent visual hierarchy.
• Change event name headers from h1 to h2 on the Common dashboard to match the Talk dashboard styling.

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Standardizes the event name header typography across the Tickets and Common dashboards by changing the event title markup from h1 to h2 to match the Talk Dashboard.

File-Level Changes

Change	Details	Files
Align event title heading level with Talk Dashboard for consistent typography across dashboards.	Change the event title container from an h1 to an h2 element in the Tickets dashboard event index template, keeping the existing inner content and logic unchanged. Change the event title container from an h1 to an h2 element in the Common dashboard event index template, keeping the existing inner content and logic unchanged.	app/eventyay/control/templates/pretixcontrol/event/index.html app/eventyay/eventyay_common/templates/eventyay_common/event/index.html

Assessment against linked issues

Issue	Objective	Addressed	Explanation
#1368	Update the Tickets Dashboard event name header to use the same typography (via heading level/styling hook) as the Talk Dashboard.	✅
#1368	Update the Common Dashboard event name header to use the same typography (via heading level/styling hook) as the Talk Dashboard.	✅

Possibly linked issues

• Match event name header font and size on Tickets and Common Dashboard to Talk Dashboard #1368: PR changes Tickets and Common event headers to h2, matching Talk Dashboard typography as requested in issue 1368.

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

Hey there - I've reviewed your changes - here's some feedback:

• Since the main event title has been downgraded to an h2, double-check the surrounding template/layout to ensure there is still a meaningful top-level h1 on these pages for semantic heading structure and accessibility.

Prompt for AI Agents

Please address the comments from this code review:

## Overall Comments
- Since the main event title has been downgraded to an h2, double-check the surrounding template/layout to ensure there is still a meaningful top-level h1 on these pages for semantic heading structure and accessibility.

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}

[Eshaan-byte]

@sourcery-ai Thanks for the review!

Regarding the h1 concern: This change aligns the Tickets and Common dashboards with the existing Talk Dashboard pattern, which also uses <h2> for the event name header. The Talk Dashboard includes <h1> elements within the dashboard content tiles themselves.

For semantic consistency across all three dashboards (which is the goal of this PR), we're maintaining this pattern. If there's a broader accessibility concern about heading structure across all dashboards, that could be addressed in a separate issue/PR that updates all three dashboards uniformly.

The primary goal here was typography consistency as requested in #1368.

[mariobehling]

Thanks. Please add screenshots showing changes.

[Copilot]

Copilot encountered an error and was unable to review this pull request. You can try again by re-requesting a review.

[Copilot]

Pull request overview

Copilot reviewed 2 out of 2 changed files in this pull request and generated no new comments.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.