Would daily challenges docs be useful?

[majestic-owl448]

I know that the daily challenges are being updated only by Tom at this time, but having documented how to add new ones, how to test, and how to release, it could be useful if someone else will ever take daily challenges on, and most of this would be useful for testing (reviewing PRs), which everyone can do, and contributors sometimes fix bugs in already released issues, for which this would also be useful

[jdwilkin4]

cc @moT01

[lakaThabrew]

Hi, I’d like to work on this documentation issue.

My plan is to add a guide covering:

• how to add new daily challenges
• how to test them locally
• how to handle release-related steps or references

Once I confirm the right location and structure in the docs site, I’ll open a PR. Please let me know if there’s any preferred page structure or scope.

[majestic-owl448]

@lakaThabrew this issue is not open for contributors, please look at issues with the help wanted label

[moT01]

not sure why, but I put them here. They should be mostly up to date, but there might be a few things off.

[majestic-owl448]

would you say it should stay as staff only docs? contributors often update these fixing typos or issues with the tests, a minimum of documentation (like the two py and js paired challenges, that they are in dev-playground, where to see them when building) could be useful?

[moT01]

yea, we could move it, or most of it, to the main docs - I think I put it there cause it describes the endpoints, and I didn't want people abusing those or something.

[majestic-owl448]

I will add to this repo the part about creating and testing, and not about the API then