I have been investigating how to add support for Web3 contact forms to my sites. I mostly have it working but now I’m wondering how the custom component can be enhanced to allow some configuration through the inspector. It would be nice to remove the hard coded pieces (color and text) into the inspector to make the component more reusable for different projects.
I noticed during the latest Dev Diary that there was a contact form being displayed in the editor, that also seemed to be using Web3. Is this something experimental or is it a sign of the future.
I need to get a rudimentary contact form on the sites I have been building with Elements. This seems like one solution. The FREE version of Web3 will meet my immediate needs.
Before I go any further with this support I’m curious to know what the future holds for contact form support in Elements. This will help make an informed decision as to whether I should proceed with what I have or wait for an Elements solution.
Web3 contact forms are rather rudimentary, but they are better than nothing. My version is a combination of HTML, Tailwind, and Javascript.
The Web3 Form Component was just me experimenting and looking at different options — We do a lot of work behind the scenes that never gets shipped.
While we didn’t want to rely on PHP for anything, we’re now thinking perhaps this would be the best route to go. Using a built-in PHP form solution means users won’t have to sign-up for a third-party service (although there is the downside of server compatibility issues).
The Contact Form Component has the most votes, so it’s what we’ve started to look at in more detail — The next question to ask is; do users want a PHP form? or one that requires signing-up for a third-party service? Cast your vote below…
Built-in PHP Form Solution
Third Party Service (like Web3)
0voters
RE the Web3 form design: If you take the raw HTML they give you, you can style it with Tailwind. If you want to make it more reusable you could break out each form element into a separate component, those could then be dropped into a form wrapper Component (hope that makes sense).
I can go either way. I do like the Web3 option because the setup is dead simple if you are using the FREE plan. This plan covers my needs. I’m not adverse to using a PHP solution but I have always found them to require a lot more setup and management.
I’ll wait to see what you come up with as it looks like most people are voting for PHP.
I agree with this - I could live with either but probably lean slightly towards Web3.
I’ve used PHP solutions in the past and found them to be fiddly to get working and to move between servers.
I’ve not used Web3 but was reading about it yesterday and it sounded like an easy, transportable solution. The only down tick from me is you need a paid solution to get file uploads.
