You Need Your Own Box

Your web developer — the person you hired or are about to hire to manage your organization's online presence — needs somewhere safe to work. Right now, if they don't have that, there is a good chance they are working on your live website. The one the public sees. The one that represents your organization every time someone searches for you.

This is not because they are careless. It is because nobody gave them an alternative.

A website is not a document. You cannot save a backup copy the way you save a Word file before you start editing. When a developer makes a change to a live site — updates a module, adjusts a configuration, tries something new — they are making that change in public. If it works, great. If it doesn't, your website is broken and the public can see that too.

The professional solution to this problem is a development environment. A separate machine where the developer can build, test, and break things without any of it touching the live site. When the work is ready — tested, confirmed, finished — it moves to the live site. Not before.

That machine is a small computer that sits in your office, costs around $200, and runs quietly in a corner doing its job. No monthly fee. No subscription. No cloud service with a pricing tier that changes next year. One purchase. Done.

But here is the part that often surprises organizations when they find out about it.

That same machine — the one your developer uses as a sandbox — can also run an internal website that only your staff can see. Not on the internet. Not accessible from outside your office network. Just yours.

Think about what your organization actually needs internally. A staff directory. A policy and procedure library that is always current. An internal calendar. A place to coordinate volunteers. A document repository that isn't a tangle of shared folders in someone's Google Drive. All of it in one place, organized the way you need it organized, accessible to your staff and nobody else.

A $200 box running Drupal can do all of that. Your developer already knows how — it's the same skills they're using to manage your public website. The machine that protects your live site from accidents is also the machine that gives your organization a real internal presence.

Two problems. One box. One afternoon. Two hundred dollars.