All my life I’ve wanted a way of comparing the contents of a site to the contents of the import file I just ingested. Imports always result in funky data, no matter how hard you try.
We’re using Github issues for all of our projects, but I still like Remember The Milk as the interface for deciding what I need to work on next. It would be neat if the two worked together.
An issue assigned to me in Github would produce a new inbox task in Remember The Milk (if one didn’t already exist with the issue in the URL field). I could then list, prioritize, and give a due date as needed. Completing the task in Remember The Milk would complete the issue in Github (and vice versa).
Idea: WordPress plugin for wp-cli so I could use the latter in the WordPress admin. Like Hopscotch, but installed on the site instead of as a browser extension. A sort of power user mode for the WordPress admin.
An idea: Use creation of WP_Error objects as a way of tracking application exceptions. If WP_Error had an action in the
__construct() method, you could easily
error_log() WP_Error codes and messages.
Can someone tell me why this is a bad idea (other than exploding your error log), or whether there’s a better approach?
I may or may not get to these in the future. If you do before me, please let me know.
Single-use P2 threads. P2 is an awesome theme for threaded conversations that stand the test of time. Avoid long, drawn out email discussions with friends by pointing everyone to a P2 thread.
A year ago you wrote… Emails of what you wrote in the past, a la Timehop.
Lock one or more dashboard widgets in place for everyone. The WordPress dashboard offers infinite customization. Sometimes you want to make sure a widget (e.g. site announcements) appears in the same place for everyone though.
Save Manage Posts filter state. It resets your query argument filters every time you navigate away.
Idea for the WordPress.com VIP ElasticSearch add-on: ability to pass arbitrary documents with external URLs to be included in the index. (ref)
Hack day project idea(s), inspired by the data science session this morning. Look at a random sample of comments across WordPress.com and…
- Classify their content (e.g. how they’re responding to the post).
- Do a topical classification of post content and compare against comment word count or frequency.
- Calculate diversity of commenters for a site as a function of unique email addresses to number of comments.
- Build a network graph indicating correlation between commenters across different sites.
The big takeaway: with any given dataset, play with visualizations first before trying to draw a conclusion.