DigiDev makes WordPress plugins that each do one thing and request the least access the platform allows. Free on WordPress.org, plain PHP you can read before you install it, no accounts to create.
01
| Plugin | Permission | Status |
|---|---|---|
|
One Folder Gallery for OneDrive
Photos from one OneDrive folder as a gallery, with albums and a lightbox. |
Files.ReadWrite.AppFolder · offline_access | On WordPress.org |
The first one is published and free. More will follow the same pattern: one job each, and the narrowest permission the platform offers.
02
Install something that connects WordPress to a cloud service and you are usually asked to grant access to everything in the account. Asking for everything is the quickest way to build it. It also means that if the plugin is compromised, or the developer's app registration is, whoever did it has your whole account.
Narrower options almost always exist. An app-scoped folder, a read-only token, a single resource instead of a directory. They cost flexibility and a good deal more work. What you get back is that a plugin with a bug in it still cannot reach anything you didn't hand it.
That is the whole product idea, and it is also why each plugin stays small. One plugin, one job, one permission. If you want a suite that does everything, I'm not building that.
03
A plugin gets the smallest scope the platform offers, even when a broader one would be easier to build against.
Your data stays where it already lives. No copies on your web server, and none on mine, because there is no server of mine.
What WordPress.org publishes is the code that runs, in plain PHP, so you can read what a plugin sends before you install it.
04
I work with an AI assistant. It writes most of the PHP. I decide what gets built, and I check the design and the data flow, in particular anything that would ask for more access than the job needs.
That is why the checking is done by tools rather than by eye. The WordPress coding standards run over the code with the security rules switched on, and the official Plugin Check has to pass. Before a release I install the plugin on a real site and use it as an administrator and as an editor. Removing it has to leave the site as it was.
The narrow permission matters here for the same reason it matters everywhere else on this page. It limits what a bug can reach.
05
Every plugin here is free and stays free. If one saves you an afternoon, you can leave a one-off tip on Ko-fi. Nobody has to, and nothing on your site changes if you don't.
A tip buys nothing in return. No supporter tier, no donor-only features, no faster answer to a question. That is deliberate: the moment a donation comes with something attached it stops being a gift and becomes a sale, with European VAT to charge and paperwork to keep. DigiDev is one person working evenings, and that is not worth the administration. So it stays a gift, and the plugins stay the same for everyone.
06
I'm Robin De Croock, a Power Platform developer in Belgium. DigiDev is what I build in my own time, on my own hardware. I don't take client work or custom development, only products anyone can install.