Add a Python documentation sprint topic

[AA-Turner]

The system doesn't permit multiple 'contacts' as far as I can tell, so I've added lines in the body text for 'contacts' -- happy to add anyone else who wants to be listed.

A

🖼️ Preview available 🖼️ : https://ep-website--1454.org.readthedocs.build/

[hugovk]

Please can you check the RTD build failure?

For example

pythonLevel**: **pythonLevel: Invalid enum value. Expected 'Any' | 'Beginner' | 'Intermediate' | 'Advanced', received 'Intermediate [Core] or Any [Documentation]'

[AA-Turner]

Sure but this seems like a restriction that should be relaxed? We need to express that beginners are fine for documentation work, but intermediate+ for core.

For an immediate fix, perhaps 'Any', and then put the actual requirements in body text rather than metadata? Thoughts @hugovk? Who's best to ask re: making 'experience' a free-text field?

A

[nikoshell]

Sure but this seems like a restriction that should be relaxed? We need to express that beginners are fine for documentation work, but intermediate+ for core.

For an immediate fix, perhaps 'Any', and then put the actual requirements in body text rather than metadata? Thoughts @hugovk? Who's best to ask re: making 'experience' a free-text field?

A

We use pythonLevel as filter field, please use description for detailed requirements.

[AA-Turner]

@nikoshell does this work?

A

[AA-Turner]

I've opened #1456 with a filtering problem I noticed.

A

[hugovk]

Looking at the preview: https://ep-website--1454.org.readthedocs.build/sprints/#heading-11

This creates three H3 headers, the latter two at a larger font, all of which appear in the side menu:

Mid-conference, a quick fix is to list them as different sprints?

[AA-Turner]

H5 fixes the sidebar issue, and the font is now the same size (though the latter two headings are in boldface). Is this OK, or should we abandon & split the pages?

A

[nikoshell]

H5 fixes the sidebar issue, and the font is now the same size (though the latter two headings are in boldface). Is this OK, or should we abandon & split the pages?

A

There is many ways to go out of boundaries, we try to handle that, thanks for reporting.
In your case I suggest to split.

fyi: PR #1458

[AA-Turner]

@nikoshell thanks, I've now split.

A

[hugovk]

Thank you! 📚