One Zip, Zero Server Access: A Self-Contained Plugin Architecture — Part III

In extensible systems, plugins often require manually copying files to the server. (Part III)

Introduction

This article examines an architecture where a plugin carries all its parts — code, sidecars, admin templates, notification channels — in a single package the administrator installs as one zip, with setup steps run automatically.

Method and Design

A manifest declares the plugin's dependencies, which the system installs automatically at install time.

Discussion

A template loader lets plugins serve their own admin pages from within the package.

The same approach applies to themes, packaged and installed as a single zip from the admin.

Enabling and disabling are safe; a disabled plugin's fields and sidecars stop cleanly.

Conclusion

Extensibility thus becomes available to administrators, not just developers.

This part demonstrates the platform's approach on a concrete journal example; the aim is to meet the complex requirements of scholarly publishing with a simple, sustainable architecture. Future work will examine how the model behaves at larger scale and across disciplines.