A page needs updating. A module needs updating. The server needs attention.
All three can arrive in the same inbox as “something wrong with the website.” They call for different kinds of work, and often different people.
Before choosing a hosting plan or website foundation, take a few minutes to name those responsibilities. You’ll have a clearer comparison and a much more useful conversation when something needs attention.
Hosting: where the website runs
Hosting provides the environment that runs your website. With a managed service, the provider takes responsibility for an agreed scope of that environment.
The useful question is what that scope includes for your project. Ask about the services you depend on, how changes are deployed, what support covers, and how problems are reported. Ask how backups and recovery work, including which parts are your responsibility.
Write down the answers for the plan you’re evaluating. The word “managed” is a starting point for the conversation; the service details tell you how the arrangement will work.
Code maintenance: keeping the foundation usable
Your website’s codebase includes the software that gives the site its structure and behavior. That foundation needs someone responsible for reviewing updates, handling dependencies, testing changes, and maintaining custom functionality.
If you bring your own Drupal codebase to Drupito, plan for your team or development partner to own that code maintenance. Clarify any additional services separately.
If you choose a marketplace website built on a maintained codebase, review the maintainer’s scope. What is part of the shared foundation? How are updates delivered? What would happen to a feature you commissioned specifically for your organization?
The answers matter most when a project grows beyond its original setup.
Content and operations: making the website useful
Someone still needs to notice when a program description becomes inaccurate, a team member leaves, or an inquiry stops reaching the right person.
Those are website operations. Name an owner for important content, user access, incoming requests, and the services your site connects to. In a small organization, one person may coordinate several of these tasks. They still need to know which tasks are theirs.
For a course website, for example, a developer might maintain the code while a program coordinator keeps dates and enrollment information current. Both are essential to a working site.
Put the handoffs in writing
A short responsibility record can prevent a long support conversation. For each important task, record an owner, a contact method, and the point at which another person gets involved.
Start with these situations:
- An editor cannot publish a page.
- A software update affects a custom feature.
- A form submission fails to reach its destination.
- The team needs to restore an earlier version of the site.
- The developer who knows the project is unavailable.
Walk through who takes the first step in each case. If everyone assumes someone else owns a task, settle it before launch.
Choose with the work in view
The right hosting and maintenance arrangement fits the people you have, the site you run, and the help you need.