4 ms·
The third option has the ability to be customised beyond the others. I have a client who needed their prospective clients to upload photos. None of the usual su
by oliwarner 2y ago
The third option has the ability to be customised beyond the others. I have a client who needed their prospective clients to upload photos. None of the usual suspects would handle that at the time. This also allows us to do client-side resizing, cropping.
On deliverability, you don't only have to send them on, you can store them in a database and build an interface onto that. If you already have a backend system (eg Django and its Admin), that's easy. Great if there are multiple people handling emails.
The downside isn't running it, it's spam.
But for another client, I skipped forms altogether. Raw email address on the contact page alongside a WhatsApp link and a phone number. Will some people drop through the cracks? Maybe.
- mmarian 2y agoI prefer the 3rd option as well, and I like the idea of avoiding email sending and just storing the data on the VM, then making it available via an interface. @superkuh had a really nice idea to just store the data in files, that way I don't have to think about which database / what schema to pick. Definitely wouldn't want to share email/phone number though. I've done it before and ended up with spam.