I hadn't seen the server side code for this yet, reproduced here:

```ruby
          trophy_updates << [concept.description, new_trophy.name, view_context.image_path(new_trophy.image_name)]
```

I really don't like to see things magic indexes like [2], unless it's mega super plainly obvious the order of things. Why isn't this an object with named keys? That's much more extensible if trophy_updates ever need to grow an extra field and much easier to understand later.