When creating new content based on archetypes, I usually start by copying the base schema, or one of my own base schemas with something like MyNewSchema = BaseSchema.copy(). One thing that has been historically hard in my case is that the schema order in the code directly correlates to the order in which its displayed. This means that the base copied data always goes first when displayed, which was not always what I wanted. The solution was custom templates and blech all over.
Apparently you can just reorder these things. Deep in the bowels of archetypes there is a function called moveField. Now, reordering the schema can me as easy as MyNewSchema.moveField('description', pos='bottom'). Hot dog! Pasting the interface for reference.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| def moveField(name, direction=None, pos=None, after=None, before=None): | |
| """Move a field | |
| name: | |
| name of the field | |
| direction: | |
| Move a field inside its schemata to the left (-1) or to the right (+1) | |
| pos: | |
| Moves a field to a position in the whole schema. pos is either a number | |
| or 'top' or 'bottom' | |
| after: | |
| Moves the field 'name' after the field 'after' | |
| before: | |
| Moves the field 'name' before the field 'before' | |
| """ |
