Revisit block definitions and play to ensure the blocks behave in a manner that is coherent and easy to understand and use.

[ntoll]

The problem:

The blocks we initially created have not been tried or tested as actual blocks to use. So far, they're mostly so Python code can be turned into blocks.

The requirement:

We need to evaluate each block to ensure we have a refined block definition that emphasises:

• Ease of comprehension
• It fits into a coherent block taxonomy
• It's clear how blocks relate to each other

The solution:

TBD

[ntoll]

Next steps:

• Agree the categories in the block taxonomy (e.g. Logic, Program flow, Builtins etc...).
• Add current blocks to a Blockly toolbox as a best effort.
• Rearrange blocks in to correct category and choose colour that reflects Scratch's a11y work and conventions.
• Check each individual block for readability / coherence (e.g. recursive dot notated references shouldn't be nested blocks but a single block that expands as more references are added to the chain of dots).

[ntoll]

@ntoll and @JoshuaLowe1002 to do first pass at EuroPython 2025 and the following Monday.