I’m mature enough to admit my mistakes, and I’m perceptive enough to recognize a cop-out when I see one.
5) Customizing the cards: Perhaps. There is limited documentation on this. So if I’m wrong here, I apologize.
6) Rearranging event categories: My apologies here. Yes, drag-and-drop is possible.
But let’s face it – most of your reply was a cop-out of your ill-conceived design:
2) Our directory/event/form shortcodes all are designed to take up an entire page…
I don’t think “used as a widget” is applicable. All I wanted to do was put events in a tabbed container. And as for that “store state in the URL” … even WordPress core can populate a page and have more than one populated list on a page. And what’s so wrong about including a feature in a widget? Maybe I want to feature a particular event in the sidebar? It’s a design flaw, plan-and-simple.
3) The directory list uses dynamic loading when a user scrolls, which we feel is better suited to today’s mobile devices than pagination.
Granted, around 50% of web traffic comes from mobile devices – but that means the other 50% is NOT. A good designer will design for more than 50% of their audience. The choice to exclude pagination is a limitation of your system.
And the biggest cop-out of all:
“Ultimately the list of things our system (or any system for that matter) cannot do is infinite…”
Are you kidding me? The features I listed aren’t unreasonable or far-fetched. Their logical uses of the system. And as I stated before, if you don’t want to provide these features, at least prepare the API so people can customize to their needs. If you don’t want to do that, then accept that people will find that your system lacks necessary features.