datopian / flowershow

💐 Publish your obsidian digital garden or any markdown site easily and elegantly.
https://flowershow.app/
MIT License
824 stars 98 forks source link

Best practice for doing forms and newsletters on Flowershow #480

Open rufuspollock opened 1 year ago

rufuspollock commented 1 year ago

Write up as a blog post (or even just in discussion forum) at least one approach for doing forms in Flowershow (and static sites in general - this isn't specific to Flowershow).

Bonus: for covering wider set of options and explaining pros and cons.

When creating a website a standard to add a signup form e.g. for registrations so that i can easily allow people to signup to my course / event / newsletter etc

When creating a webssite I want to have a newsletter (? what does this mean) so that people can keep up to date with what i am doing

Acceptance

Tasks

Notes

Discussed in https://github.com/flowershow/flowershow/discussions/469

Originally posted by **rufuspollock** March 30, 2023 What are the options for forms for Flowershow sites? Would love some documentation about this (later we can migrate to docs) ... so that we know best practice (and options) for doing forms going forward - [ ] Using netlify forms - [ ] Using sendinblue - [ ] Using jamstack forms services e.g. getbasin etc - [ ] ... Things to answer - [ ] What have people tried out - [ ] What are pros / cons? - [ ] What is recommended approach? - [ ] Howtos for specific cases @khalilcodes @olayway can you share your notes / experiences ...