pyrocms/pyrocms — comment on commit 96ef9793b580b7c7d7dae56062f2094e03deebad
File:  line 0
By jerel:

The biggest problem with the old form was this: you had Name, Email, Company Name, Subject, and Message. And that was it. Many many people asked how they could add a field. Or remove one. With this approach you can add any number of text, dropdown, text area, and file fields.

With this one the designer lays out the form himself. He can wrap each field with whatever he desires. He can create just the fields that he needs and embed the form anywhere. It can go in the layout file, in the footer, wherever as it submits to the current_url() (unless you override it and send it to a controller somewhere else, like a contact page that contains the same tags). If you want it in a Page you can include an html file and tell the site manager to paste it into page content.

I do see where you're coming from if a site manager switches themes the contact form may lose its style since one designer may specify different classes than another. He may have even used different field names. So that's a good point. In my opinion tho the flexibility of it outways the disadvantages