Support and Maintenance en Geneva
How we work in Geneva
Content versions, not just server backups
A backup restores the whole site as it stood last night, and for three deleted paragraphs that is far too blunt an instrument: you would wipe out everything the others did during the day. Versioning keeps each page separately and lets you return that one page, and only that one, to yesterday's state.
Who changed what and when, without having to ask
A log for each page with the person, the date and what was touched. It is not there to point fingers: it is there so the question gets answered by looking at a screen, instead of opening a twenty-message thread in which hardly anyone remembers.
Going back is a procedure, not an improvisation
It is settled in advance who can restore, whether permission is needed — for returning to the last approved version, usually not — and where it gets recorded. When something goes wrong, arguing about who is allowed to fix it costs more minutes than the fix itself. We rehearse it with you once, calmly.
Access expires because people move on
A quarterly review of who can get into what: the colleague who changed roles, the previous supplier, last summer's intern. A role nobody uses any more is still an open door. It takes half an hour every three months, and it is the first thing we find missing when we take over somebody else's site.
Answering your questions
What people ask us about Support and Maintenance in Geneva.
If your question is not here, tell us about the project and we will answer with real context.
Ask us directlyReal work
Projects we have built
Full service · All the detail
Support and Maintenance: stack, process, use cases and FAQs