My thoughts:
Naming convention:
h/<setName>_<numberOrName>.dat
Description:
No prefix, the 'h/' folder already indicates it's a non standard part.
If we put "Helper" in the category meta the description can be free to fill in by the author.
Maybe only use a prefix to indicate the 'set' of helpers it belong to, but even this should be up to the author of the set.
Category:
I would recommend making this mandatory "HELPER", so the description if free to use.
Keywords:
The type or "qualifier" should be put here, e.g. "3D arrow", "2D arrow", "Arrow" (can be together with 2D arrow).
Location:
<LibraryRoot>/parts/h
Design:
Only orientation should be formalized.
Dimensions:
Again up to the author imho.
In short I would like to leave as much freedom to the helper (set) authors as possible.
Naming convention:
h/<setName>_<numberOrName>.dat
Description:
No prefix, the 'h/' folder already indicates it's a non standard part.
If we put "Helper" in the category meta the description can be free to fill in by the author.
Maybe only use a prefix to indicate the 'set' of helpers it belong to, but even this should be up to the author of the set.
Category:
I would recommend making this mandatory "HELPER", so the description if free to use.
Keywords:
The type or "qualifier" should be put here, e.g. "3D arrow", "2D arrow", "Arrow" (can be together with 2D arrow).
Location:
<LibraryRoot>/parts/h
Design:
Only orientation should be formalized.
Dimensions:
Again up to the author imho.
In short I would like to leave as much freedom to the helper (set) authors as possible.