Future plans and thoughts from everyone.

Future Development Thoughts/Community Input

Hi there, I'm Ben the new in-house Shorthand Integrations engineer. My role is largely maintaining and improving all things Shorthand integration; Drupal, Wordpress, general API updates etc.

As I've been slowly getting up to speed with all things Shorthand (and by extension Drupal) I've been looking over how Drupal and Shorthand work together and gauging from the community response/questions there's room to improve, particularly when it comes to having the module do things the "drupal way". (I was almost going to make this post a piggyback off of issue #3197751 but felt the discussion can exist in a more broader context.)

From discussions with past creators/contributors to this module it seems that everyone is keen to see the module move into a more fragmentary approach; i.e. rather than request a giant dump of html and assets to sift through, the module could grab sections/assets partially and store them in the appropriate Drupal locations/modules - the node vs entity issue is relevant here.

As well as this shift I'm keen to see what other thoughts the Shorthand module community has particularly around other use cases.
For example; adding the ability to flag externally hosted assets - i.e. have the module pluck the assets from shorthand but store them in a 3rd party CDN/location for file-size limit reasons.

Looking forward to seeing what y'all are thinking! In the mean time I'll be pushing up some monkey patches for things and adding quick bits and pieces; nothing too major without this community discussion first.