Search Results for "forms"

Keila is a fully open-source newsletter platform designed as a self-hosted alternative to services like Mailchimp or Sendinblue. It enables users to create and manage email campaigns, build customizable signup forms, and handle subscriber lists. Keila supports using a personal SMTP inbox for small-scale newsletters or integrating with major transactional email providers—AWS SES, Sendgrid, Mailgun, Postmark—for larger deployments. It offers a sleek WYSIWYG editor for campaign creation, version 0.17 adding features like mobile/desktop preview, preview emails, French localization, API enhancements, external contact IDs, and update notifications. ...

Kaffy is an Elixir/Phoenix library that provides a powerful, customizable admin interface with minimal setup. Inspired by Django’s built-in admin and Rails’ ActiveAdmin, it allows developers to manage data models, forms, dashboards, and navigation without altering their existing codebase. Kaffy auto-generates CRUD interfaces for your Ecto schemas, supports advanced customizations, and integrates seamlessly with Phoenix projects. It’s designed to be both simple for quick setup and flexible enough for complex admin needs.

...It provides straightforward encode and decode functions, along with a protocol-based encoder that lets you customize how your structs become JSON. Developers can derive or implement Poison.Encoder for domain types, control which fields are included, and map complex values into JSON-friendly forms. On the decoding side, it supports options for key handling and flexible parsing of JSON into Elixir maps, lists, and primitive values. Internally it uses optimized binary processing to keep allocations low and throughput high, which is why it became a popular choice in early Elixir ecosystems. The API is intentionally small and unsurprising, making it easy to drop into controllers, background jobs, or data pipelines. ...

An Elixir implementation of Facebook's GraphQL. This is the core GraphQL query parsing and execution engine whose goal is to be transport, server and datastore agnostic. In order to setup an HTTP server (ie Phoenix) to handle GraphQL queries you will need plug_graphql. Examples for Phoenix can be found at hello_graphql_phoenix, so look here for a starting point for writing your own schemas. Other ways of handling queries will be added in due course. Tokenization is done with leex and parsing...