Skip to content

Independent · open source · since 2020

We build small WordPress plugins properly

TechZigya is a small WordPress shop. We make focused, free plugins and hold them to a standard the ecosystem does not always insist on.

// How we work

Four decisions, made once

These are settled before a line of a plugin gets written, rather than argued about afterwards.

01

One job per plugin

A plugin that tries to do everything ends up doing most of it badly. Ours have narrow scope on purpose. When we are tempted to bolt something on, we ask whether it belongs in a different plugin.

02

Standards first

We build on WordPress’s own APIs, follow the coding standards, and internationalise from the start. That is what makes a plugin survive a core update and behave predictably alongside the forty other plugins on a real site.

03

Accessible because it matters

Keyboard operability, correct ARIA roles, meaning that does not depend on colour, and respect for reduced motion are part of how we build. If a block cannot be used without a mouse, it is not finished.

04

Free means free

GPL licensed and free on as many sites as you like. No feature held back behind a banner, and no licence key to lose.

// The fine print

What “free” means here

It is a word that has been stretched a long way by WordPress plugins. This is what we mean by it.

No feature held back

There is no paid tier behind a banner in the settings screen. What the plugin does is what you get.

No account, no licence key

Nothing to register, and no key that stops working when a subscription lapses.

No calls home

The plugins make no external requests. Editors, fonts and libraries are bundled and served from your own site.

GPL, and readable

No obfuscated or minified-only code. The source for everything compiled ships inside the plugin.

// Where we are

A small shop in Kathmandu

TechZigya is run out of Kathmandu, Nepal. The plugins are built and maintained by a small team, which is the reason there are three of them rather than thirty, and the reason a bug report reaches the person who wrote the code rather than a queue.

If you are using one of these on a client site and something is in your way, tell us. We would rather hear it than not.

Based in

Kathmandu, Nepal

Plugins published

Three, all free

Licence

GPLv2 / GPLv3

Support

Direct, via the contact form

Work with us

Bug reports, feature requests, and custom WordPress work — all welcome.