DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to collect enquiries and newsletter sign-ups without cookies with Kaletacms

Add an enquiry form and double opt-in newsletter to a business site, then send confirmed subscribers to your mailing service.

Who it is forA marketer or owner of a service business who wants leads and newsletter subscribers without CAPTCHA or cookie banners.

The problemContact forms and newsletter sign-ups usually need CAPTCHA, cookies and third-party scripts, which add friction and privacy concerns.

The outcomeEnquiries reach the admin and by e-mail, and confirmed newsletter subscribers are passed to your mailing service.

What you need first

  • Hosting with PHP 8.3 or newer and MySQL 8 or MariaDB 10.6 or newer
  • FTP access to the hosting and a way to create an empty database
  • The kaleta-X.Y.Z.zip file from the GitHub Releases page

Steps

  1. Install Kaleta and add a contact section with a form to a page in the page builder.
  2. Set up email notifications for enquiries in the admin and check the CSV export.
  3. Enable the newsletter and confirm that sign-ups use double opt-in.
  4. Connect your mailing service, such as Brevo, MailerLite, Mailchimp, Ecomail or SmartEmailing, or use a webhook to pass confirmed subscribers on.

Prompt for your agent

Using the kaletacms repository, set up the enquiry form and double opt-in newsletter on my Kaleta site at <site-url>. Expected output: a list of the form fields and the mailing service I connected, and verify by submitting one test enquiry and one test sign-up.

Caveat. The README says newsletters go to Brevo, MailerLite, Mailchimp, Ecomail, SmartEmailing or any service via a webhook, but it does not give connection details, so confirm the exact setup in the user guide.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page