royallthefourth / quicklist Goto Github PK

The unique message count on /list/view/1 shows the total number of deliveries, not messages.

Add CLI command to bulk remove contacts

A web API with all the features of the command line would be useful. Probably ought to have multiple per-user tokens.

We don't have a 404 page yet. Just needs an action and a layout.

Table with number of contacts and number of messages.
Each sum links to a paginated index of:

• contacts
• messages
• deliveries

Table of deliveries by scheduled send date with links to contact, message, and list

• get handler
• route generator
• route config
• layout
• menu entry

A page that shows a single list and links to its messages, contacts, and deliveries

• Subject and body entry
• Return to message detail page

• Message edit layout
• Message add GET handler
• Message add POST handler
• Message edit GET handler
• Message edit POST handler

SMTP is really slow and the delivery queue should stop itself if it runs too close to the next cron. Perhaps a 55 second limit would be useful.

OFFSET performances degrades proportional to the distance of the page you're requesting. Rewrite these per section 3.1: https://sqlite.org/rowvalue.html

Add a signup widget that can be embedded on a website. Each widget probably needs a list of authorized domains.

Paginated table of all messages on a list

Make sure every page looks and feels correct on mobile

Make sure users cannot trigger unwanted updates by passing the wrong values (eg empty string) to DB functions

• Show the contents of a message
• Table of delivery info
• Message edit button
• Sent-to-list miniform

Make note of all the WHERE and ORDER BY conditions to find the most commonly used

Commands should line up better with web interactions. Some like contact:add are pointless and don't belong at all.

System messages (eg optins) use the delivery queue for SMTP throttling purposes, but really don't belong in the reports. Add a system BOOLEAN column to messages and filter it out of all associated reports.

Users (currently managed entirely by CLI) need to be able to login and logout of the web GUI

Direct database interaction should only happen inside the Db namespace functions.
The Db functions should only be used within the console commands and request handlers.

Need working unsubscribe actions

• Contact list page
• Contact detail page

Each layout class should validate or filter all inputs that come out on the page

• Add migration converting body to text_body and adding html_body
• Update send function to appropriately send text or multipart messages
• Add detail/summary blocks for show/hide of the text body, html body, and HTML preview
• Add iframe that shows a preview
• Add JS that posts the current HTML to the preview frame
• Add a page that echoes whatever output is sent to it for HTML previews
• Add a comfortable, syntax highlighted editor for the HTML entry box

Having to recreate test data is getting old quick. Need to write a seeder to insert reasonable-looking test data. Maybe two different seeders: one to test UX on small datasets and another for large ones.

• route function
• route config
• link from list view page to "add contacts"
• layout with textarea and instructions to add one email per line
• send optin messages checkbox
• get handler
• post handler

List messages with a link to each message

• Put a link on the list index page to "new list"
• Display a form
• Insert the new list

Paginated table of all contacts on list

• Show recently added contacts, link to all list contacts page
• Show list of recently sent messages, link to all list messages page

The message page "send to list" form should send the user over to a "schedule delivery" page

• url generator
• route definition
• get handler
• form layout with prefilled date/time, message subject, and list name
• post handler