title sizes improvement

[Kxljxv]

What Needs Improvement?

The title sizes are very inconsistent and often too small on the event doc pages.

Proposed Improvement

Title sizes should always be "#" for the overall title, "##" for About the Event, Rules, Commands, Q&A, etc., and for anything subordinated to that "###". Because the rules are very important, they could be made bold.
For example (in craftattack-cube-building.md):

Benefits of the Improvement

This makes the documentation clearer for the user. Also, some pages have different title sizes than others.

Additional Context

No response

[TheBjoRedCraft]

Hey Koljav,

first of all, thank you so much for taking the time to think critically about how the documentation could be improved. Your observation about the inconsistency in title sizes is absolutely valid, and it’s great to see contributors paying close attention to the user experience.

However, I have to explain why we unfortunately cannot simply apply the proposed changes as they are.

Reason 1: Existing Documentation Standards

We currently have a set of internal style guidelines that govern how documentation is structured, including heading hierarchies, formatting conventions, and content layout. These guidelines are aligned across multiple teams and projects to ensure a consistent experience for users, contributors, and maintainers.
Changing the heading levels on an individual page, even with the best intentions, would create a discrepancy between documents, which could confuse readers or cause problems for automated systems that rely on this structure.

Reason 2: Automated Systems Dependency

Some parts of our documentation platform rely on automatically parsing heading levels to generate table of contents, navigation aids, and SEO metadata.
Adjusting the heading levels manually could potentially break these features or cause issues that are hard to debug. Unfortunately, the documentation isn't purely static content — it’s dynamically processed, so every change to the structure must be considered with technical dependencies in mind.

Reason 3: Broader Implications

If we allow direct manual formatting changes here, it sets a precedent that could result in fragmented documentation over time. We need to ensure that all formatting changes happen through a centralized process, so the entire system stays maintainable as it grows.

---

Next Steps

That being said, your feedback is genuinely valuable!
I will forward your suggestion to the documentation maintenance team for review. If they agree that the heading hierarchy could be improved across the board, it might lead to a larger, standardized update that benefits all event documentation equally.

If you'd like, you're more than welcome to help by drafting a general proposal that could be discussed in the documentation working group, where larger structural decisions are made.

---

[Kxljxv]

It seems, that the text standing there could make sense.