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.

@vmcj vmcj requested review from eldering and meisterT November 8, 2025 16:27
Use the |problemseturlteam| page to get:

- 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,
Copy link
Contributor

Choose a reason for hiding this comment

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

I like the brevity of this explanation, but I'm not sure if we might want to include a hint that more information is available when hovering the indicators.

Copy link
Member Author

Choose a reason for hiding this comment

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

Feel free to propose an alternative text.

.. |DOMjudge| replace:: DOMjudge
.. |baseurlteam| replace:: https://example.com/domjudge/team
.. |problemseturlteam| replace:: https://example.com/domjudge/team/problems
Copy link
Member

Choose a reason for hiding this comment

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

Do we need to mention the URL? It's in the menu, nobody should need to enter more than the base URL anyway.

.. |PROCLIMIT| replace:: 64

""" % (baseurl_separator, baseurl_separator)
""" % tuple(['/' if '@BASEURL@'[-1]!='/' else '']*2)
Copy link
Member

Choose a reason for hiding this comment

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

Not sure what this is used for, and the commit doesn't explain it

requests and replies is done through the web interface at
|baseurlteam|.

Use the |problemseturlteam| page to get:
Copy link
Member

Choose a reason for hiding this comment

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

Leave the URL out here (as mentioned on the other commit)

Use the |problemseturlteam| page to get:

- 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,
Copy link
Member

Choose a reason for hiding this comment

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

What about something like this?

- view indicators for problem difficulty (submission and acceptance rates) across contest intervals (hover over the boxes for exact numbers),

@vmcj
Copy link
Member Author

vmcj commented Nov 27, 2025

domjudge-team-manual.pdf

Final manual.

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.

5 participants