Skip to main content
May 13, 2025 | Ryan De La Torre | Engineering | New Features We’re excited about our new team members and a new repo structure!

​
New Team Members!

We’re excited to announce that three new members have joined the Design System team!
  • Helen Holmes, design
    ”Helen has been working on design systems for the past six years with the New York Public Library and Modern Treasury. In her free time she makes graphics for her local transit advocacy group.”
  • Adam Lantz, engineering
    ”Adam brings with him 9 years of experience in frontend development and design systems. He’s an avid traveler and lifelong learner.”
  • Erica Gugliemella, engineering
    ”Erica had been leveling up at digital agencies over the past 15 years to build a front end tech and accessibility focused career. She is excited to bring her knowledge to ST to help expand their inclusive product footprint.”
Helen, Adam, and Erica were hired to the Design System team in Q1 of this year and they’ve already been making fantastic contributions to our code and processes. Make sure to give them a warm welcome!

​
Anvil2 Repo Migrated into Hammer Repo

If you’ve contributed to Anvil2 in the past, you might remember that Anvil2 was split across two separate GitHub repos—-one for Hammer, which is our base library and one for our ST-specific Anvil2 library. Going forward, both codebases will exist together in one repo. Our hope is that this will make working on our codebase much easier and more efficient!
A couple technical notes on the merge:
  • anvil2 is now a package in hammer. The previous anvil2 code can all be found in hammer repo in the packages/anvil2 directory. Please pardon our dust as we clean up some of files that are no longer relevant after the migration.
  • Git history is preserved. If you made a commit to the previous anvil2 repo, that commit should also be reflected with regard to the imported files in the hammer repo.
  • pnpm for package management. The hammer and anvil2 repos previously used different package managers. The new combined hammer repo is now using pnpm for the entire repo. To contribute to the codebase, you will first need to install pnpm if you haven’t already.
  • Changesets for versioning. The hammer and anvil2 repos also used different tooling for managing changelogs and version bumps. The new combined hammer repo is using Changesets, and we’ve added a GitHub PR bot to let you know if your PR is missing a changeset file.
If you’re just getting started contributing to the Hammer/Anvil2 monorepo, all of this information and more is documented in our new Contributors Guide.

​
README and Contributors Guide

As part of cleaning up our repo, we’re also been updating our README files. Our new root-level README.md is now a hub with links to everywhere you might want to go, including links to our documentation and our support channels. It also displays the most recent version of the Anvil2 npm package and links to the changelogs for each package that we publish.
A lot of the information that was previously in the README.md file was directed at contributors, but as part of this cleanup, our contribution documentation has been moved to its own CONTRIBUTING.md file!
This Contribution Guide should cover everything from running our Storybook instance to running our unit tests to making your first pull request. If anything is unclear, please reach out so we can update the guide! Our hope is that this will make finding what you’re looking for much clearer than it was previously. If you want information on importing and using the Anvil2 package, that information is in our docs. If you want information on contributing to Anvil2, that information is in the CONTRIBUTING.md file. And our README.md links to both places.

​
More Updates Coming Soon!

In addition to making things better for everyone who might be contributing, we’re also gearing up for some big updates to our implementation docs in Q2! We’re excited to build a much stronger integration between our Storybook and our implementation docs, which should result in even more useful code examples that are updated much more frequently. We’re also working a number of anticipated new components such as Drag-and-Drop, Table, Drilldown, NumberField, TimeField, and a days-of-the-week component. Please look forward to even more components, better docs, easier contribution, and more in the coming months!
Last modified on January 23, 2026