Cilantrobyte.

Tech Stacks · Frontend

jQuery

Legacy maintenance, not new builds.

Category

Frontend

At the studio

Since 2019

Projects shipped

Numerous

Status

Active

(01) Our take

jQuery isn't dead — it powers a meaningful slice of the web, including a lot of WordPress, a lot of enterprise intranets, and a lot of codebases that were modern in 2014 and just kept shipping. When we inherit a jQuery codebase, we work in it competently rather than insisting on a rewrite we can't justify.

We won't use jQuery in a new project. Modern browsers have closed the gap it was invented to fill, and the hiring signal of a new jQuery codebase in 2026 is one we'd rather not send. But for maintenance, feature work, and incremental modernisation of existing codebases, we'll show up and do the work well.

(02) What we build with it

Typical work

  • Maintenance and feature work on existing jQuery codebases
  • WordPress theme and plugin JavaScript
  • Incremental modernisation from jQuery to vanilla JS or React
  • Legacy enterprise intranet feature development

(03) How we engage

Engagement shape

Scoped as advisory retainers or fixed-scope maintenance sprints. We rarely quote more than 8 weeks of jQuery work without including a modernisation phase.

Thinking about a jQuery project?