PythonIreland / PythonIreland/2026.pycon.ie

Fix inverted heading hierarchy in Code of Conduct

Open Beginner friendly
#14 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

content priority: medium seo
Dominant language
HTML
Stars
1
Forks
0
Avg merge
10m
Merged PRs (30d)
1

Description

Problem

content/code-of-conduct/_index.md (forked from an external template) has its heading levels inverted: H3 elements appear as top-level sections, and H2 elements appear inside what are logically subsections.

Specifically:

  • ### Python Ireland Code of Conduct (H3 — should be removed, H1 is set by template)
  • ### The Short Version (H3 — should be H2)
  • ### The Long Version (H3 — should be H2)
  • ### Contact Information (H3 — should be H2)
  • ## Attendee Procedure for incident handling (H2 — appears inside a section, should be H3)
  • ## Staff Procedure for incident handling (H2 — same issue)

A quality rater checking heading structure would flag this as a structural error.

Additional fix

The document states "As of 2025, the committee consists of..." — update to 2026.

Also verify the Ada Initiative links (referenced in the staff procedure section) — these may be dead links since the geekfeminism.wikia.com migration.

Files to change

  • content/code-of-conduct/_index.md

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

Open content/code-of-conduct/_index.md and inspect the heading hierarchy, the 2026 committee statement, and the Ada Initiative links in the staff procedure section. Compare the headings with the structure listed in the issue, verify whether the links still resolve, and confirm the file has the corrected levels, year, and links.

Written by the indexing model from the issue text.

Assessment

Domain
documentation
Issue type
Documentation
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
78/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.