Web Design and Development en San Francisco
How we work in San Francisco
Code gets no choice of spelling; your text does
Style sheet properties and function names are set by the specification: there is nothing to choose there. The choice is in what a person reads. Mixing up the two layers is what produces the site where somebody “corrected” a technical name and broke the styling.
Every visible string comes from one place
If the text is buried in twenty templates, switching spelling means digging through the repository and hoping you missed nothing. With a single string catalog, the review is reading one list. Laravel ships with it; in React or Next.js you set it up on day one.
“en-US” and “en-GB” are tags that actually do something
A page's language tag accepts a region, and the browser uses it as a hint for the spell checker in text fields. Plain “en” is not wrong, but it declines to say which of the two. If the site is aimed at the United States, say so.
The spelling is also in the buttons nobody wrote
Browser validation messages, the default strings in a form library, whatever an off-the-shelf component says. They arrive in the spelling of whoever wrote them and never get reviewed, because they are not in the copy document anyone signed off on.
Answering your questions
What people ask us about Web Design and Development 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
Web Design and Development: stack, process, use cases and FAQs