Series: Thoughts and Proof of Concepts

In WordPress we have a lot of options to create contact forms. But I can’t seem to find the best solutions. I even think to create my own contact forms plugin.

My Requirements Are:

1. Responsive.
   Not only in form output/front-end. Administration panel need to work in mobile devices. Well, at least usable, I understand that some features might need to be hidden/disabled in small screen devices for usability and UX. But not broken.
2. Use WordPress UI:
   Seamless integration with WordPress, native-feel. I’m not a fan of app-like fancy UI. Professional. No excessive branding with cute icon/logo. If possible no cross-selling of add-ons/upgrade (or easy way to disable it).
3. Simple and easy to use:
   User need to be able to use it without the need to learn proper form HTML markup.
4. Little to no learning curve:
   No excessive features, I just need a contact form not a shopping cart, not a user registration form. If the code base is extendable and able to do all this via add-on that’s a plus. But it’s not necessary and not needed in the “core” plugins.
5. Theme and Template Friendly:
   Can be added in a page template, any template file, no need to be in the “loop”. Simple shortcode to display the form should work with do_shortcode() function.

So, basically, something basic that I can use on my clients site and that’s it.

Of course anti spam features (maybe custom honey pot or integration with recaptcha/akismet) is also a requirements.

Here are several of my issue with current contact forms solutions (not in particular order):

Read More Help! I Can’t Find The Right WordPress Contact Form Plugin

I didn’t ask this question a lot. But recently a client linked to an article, possibly to make sure I didn’t ask for their estimate budget for the project (which is fine):

The Worst Question To Ask Your Clients: “What’s Your Budget?”

The article covers some valid points. Asking budget question might be a sign for:

1. Lack of knowledge
2. Signal of deception
3. No value
4. No due diligence, etc.

But I don’t always agree. In some case asking for budget is totally fine. Read More Why Do We Ask: What’s Your Budget?

Recently WordPress plugin review team write a reminder post “Please do not submit frameworks” (Ipstenu/Mika Epstein).

And the reason is:

We require that plugins be useful in and of themselves (even if only being a portal to an external service). And while there are many benefits to frameworks and libraries, without plugin dependency support in core or the directory, it becomes another level of hassle for users.

In a comment, Darrin, who had a framework plugin (Advanced Term Fields) submitted and approved last month asked:

Are you saying the best way to handle this scenario is to include the parent framework in each child plugin, as opposed to alerting the user that “This plugin requires XXX plugin in order to function properly”?

And Mika answered:

Currently, yes. That would have been the best way.

I don’t really agree with this.
I think it should go to the opposite direction. And this is why. Read More I think WordPress plugin review team decision to no longer accept framework is wrong. And this is why.