Support and Maintenance en San Francisco
How we work in San Francisco
The other form returns as soon as several people write
It is nobody's carelessness: everyone writes the way they learned. Two years in, a site with no verification has both spellings scattered across new pages, release notes and one-off announcements. This rule does not hold up on good intentions, but on an automated step.
A warning before publishing, with a short list
We add a check to the publishing process that looks for the ruled-out forms in the text that changed and warns before it goes out. It corrects nothing on its own: it flags and lets the writer decide. It is one of the cheapest checks in existence.
Third-party pieces arrive with their own
The cookie notice, the support chat, the payment gateway and the embedded search write what they write, and several will not let you change it fully. You review which accept your own text and which you have to live with. What does not work is never having looked.
A misconfigured dictionary underlines what is right
An editor pointed at the opposite variety marks the correctly spelled words in red, and by the third time somebody “fixes” them in perfectly good faith. That is why the dictionary configuration lives in the repository and not on each person's machine.
Answering your questions
What people ask us about Support and Maintenance in San Francisco.
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
More services in San Francisco
Full service · All the detail
Support and Maintenance: stack, process, use cases and FAQs