Bill W:
Chad G:
#8 of 21 in a series: Building SOAPSzone
Story Idea #100 – Building the WordPress Plugin: Importing Media from Google Drive Into SOAPSzone
The SOAPSzone backroom lives heavily in Google Drive. The public site lives in WordPress.
Those two facts create a predictable nuisance: moving finished media from the working archive into the website.
Rather than repeatedly downloading a file to one computer and uploading it again to WordPress, we want to explore a plugin that can import selected media directly from the project’s Drive workflow.
The article will follow the plugin from problem definition through implementation. How should authentication work? Which folders should be visible? Should the plugin copy an image into the WordPress media library or reference it remotely? How do we preserve filenames, captions, source and attribution information? What happens when a Drive file is later changed or deleted?
Security matters too. The WordPress site should never need broad access to private material merely to import a photograph from an approved folder. Permissions should be as narrow as practical.
This small technical project illustrates a larger theme in building SOAPSzone: tools become valuable when they remove repeated friction from the publishing pipeline. Saving a couple of minutes on one image is trivial. Saving those minutes hundreds of times—and reducing the chance of attaching the wrong version or losing attribution—is not.
We also intend to document what fails. Plugin development has an excellent way of revealing assumptions that seemed obvious five minutes earlier.
The finished result may be useful only inside SOAPSzone, or it may become something more general. Either way, the build itself is part of the Zero-to-60 story: identify a repetitive task, create the missing tool, and then see whether reality agrees with the design.
