context

C1: "Content" with "The content to execute" is enough for a developer macro. The description does not say that the source parameter can replace it.

C2: not mandatory, since the source parameter can give the content instead.

C4: a plain text area in the Edit Macro dialog, counted under E6.

C6: first in the dialog, which is the order of the most common example.

C1, minor: the description "The reference to the page the content will be executed in." does not say what an empty value does, although both calls of the XWiki sources outside the tests leave it empty and keep the current page, like {{context restricted="true" source="script:tip"/}} .

C4: a page picker that shows the title of the chosen page, "Context fixture page" for the audit page. The macro itself takes a plain string and accepts any value, see E2.

C6: first after the content, and set by the most common example.

C1: "Indicate if the content should be executed in a restricted context." uses a technical term, which is acceptable for a developer macro. The French name and description are left in English, which is a translation matter, not recorded here.

C8: not advanced, and set by two of the real calls of the XWiki sources, like {{context transformationContext="document" restricted=true}} .

C1, minor: the description "the reference of the content to insert (e.g. string:bold, script:myvariable)" gives two examples of the "type:value" syntax but does not list the other types, and does not say that the source replaces the content. The error "Unsupported source type [foo]" is the only way to learn the other types. The French name and description are left in English, a translation matter.

C4: a free text field for a typed reference, with no picker for the types that could have one, like a page: the user has to know the syntax. Some types, like script:, cannot have a picker, so a proper field needs design work, as for the code macro.

C7: the source and the content are alternative ways to give the content, but the Edit Macro dialog cannot present them as one choice, since only parameters can be part of a feature. A limitation of the macro system, listed in the Cross-macro findings, reported as XWIKI-25456.

C8: advanced, as it is used by a minority of the calls, like {{context restricted="true" source="script:tip"/}} .

C1: the dialog shows the name "TransformationContext" in camel case, and the description "The Transformation Context mode to use. Valid values are "current", "document" and "transformations"" repeats the name and lists the values without saying what each one does, or which one to pick: the three modes change which XDOM the macros inside the content see, and "transformations" executes the macros of the other page. The documentation explains them, the dialog does not. The values appear as "Current", "Document" and "Transformations" in the select, while the description writes them in lower case.

C3: Current is preselected, the declared default.