Skip to content

Conversation

@vmcj
Copy link
Member

@vmcj vmcj commented Oct 28, 2025

This was mentioned by @meisterT in another PR, so this is a start of documenting the /problems page. I removed the pascal example as it forces us to another page and I suspect it's never needed (not sure how many tries it will save in a year).

The resulting PDF:
domjudge-team-manual.pdf


- all attachments such as 'testing tools' to problems,
- view the submission and acceptance ratio during the contest as an indicator of the difficulty of a problem,
- get the problem statement and clarifications on those statements
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Either add a comma at the end here or remove it from the first two lines.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I went with the extra comma.

.. figure:: team-problemset.png
:width: 80%

The problem set webpage.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
The problem set webpage.
The problemset webpage.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I looked that one up and it seems that 'problem set' is the correct form and 'problemset' is something which is informally accepted. I'm fine with both though.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The UI uses problemset it seems so that's why I'm suggesting it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants