Change the naming of the filters, head_{...}, content_{...}, and foot_{...}

[michaeluno]

head_ + page slug – receives the output of the top part of the page.
head_ + page slug + _ + tab slug – receives the output of the top part of the page.
head_ + extended class name – receives the output of the top part of the page, applied to all pages created by the instantiated class object.
content_ + page slug – receives the output of the middle part of the page including form input fields.
content_ + page slug + _ + tab slug – receives the output of the middle part of the page including form input fields.
content_ + extended class name – receives the output of the middle part of the page, applied to all pages created by the instantiated class object.
foot_ + page slug – receives the output of the bottom part of the page.
foot_ + page slug + _ + tab slug – receives the output of the bottom part of the page.
foot_ + extended class name – receives the output of the bottom part of the page, applied to all pages created by the instantiated class object.

The words, head and foot might not be the best naming choices for these filters because they often remind of the head and foot HTML tags, not the positions.

So instead of head, content, and foot, it might be better to replace them with top, middle, and bottom.

[Edit]
Now I started to think top_{...}, middle_{...}, and bottom_{...} are not enough either because they won't remind of string contents. Maybe top_content_{...}, middle_content_{...}, and bottom_content_{...} could be better. I don't know.

[michaeluno]

At this time, they will be:

• content_top_{...}
• content_{...}
• content_bottom_{...}

If you have a better idea, it should be addressed before v3 gets released.

[michaeluno]

Done.

[michaeluno]

Now I think

• content_head_{...}
• content_{...}
• content_foot_{...}

is better.

[michaeluno]

Done.