Documentation Index
Fetch the complete documentation index at: https://anvil.servicetitan.com/llms.txt
Use this file to discover all available pages before exploring further.
Usage Guidance
Use this section to understand what support is available, how to engage with us, and how we prioritize our time and resources to keep Anvil2 healthy and effective.Weekly On-call Support
We run a weekly on-call rotation to provide fast, reliable support to product teams. Each week, 2 designated Anvil team members are responsible for:- Responding promptly to questions in Slack (#ask-designsystem
- Hosting office hours
- Assisting with implementation questions
- Capturing new requests or system gaps
- The on-call partner escalates complex issues to the relevant team member as needed to unblock consumers.
Weekly Office Hours
We host several scheduled office-hour slots each week where consumers can meet with the Anvil2 team. Teams often use these sessions to:- Walk through designs, implementations, or bugs
- Walk through feature requests
- Get feedback on patterns or components
- Check accessibility behavior
- Review early concepts
- Resolve visual or interaction issues
- Support code implementations
Quarterly design resource rotation
We rotate design resources on a quarterly basis to focus on priority workflows and provide deep, consistent support to the areas that impacts ServiceTitan’s core priorities. Each quarter, specific Anvil2 Design Technologists are assigned to priority workflow groups, enabling:- Deeper partnership with product teams
- Hands-on involvement in real product design
- Stronger pattern identification and reuse
- More informed system improvements
- Exposure to different workflow needs over time
- Dispatch
- CSR
- Technician
- End-to-end teams: TI and Global Search, Navigation
- Memberships and Service Agreements
- SalesPro
- Toolbelt
How we prioritize work
We prioritize work based on:- Impact to the user
- Alignment with manifesto
- Impact across multiple product teams
- Accessibility or usability concerns
- Duplicated effort or system friction
- Long-term maintainability
- Contribution volume and urgency
- Repeated support requests
How we collaborate with teams
We support consuming teams by:- Joining team reviews, supporting implementation
- Teaming up on bugs
- Providing async guidance in Slack
- Running office hours
- Participating in discovery or planning discussions
- Reviewing component and pattern usage
How we support contributions
Any team can propose new features, enhancements, or improvements to the design system. Our contribution workflow includes:- Understanding the problem
- Checking alignment with system principles
- Reviewing system-wide impact
- Exploring options collaboratively
- Validating accessibility and engineering feasibility
- Collaborating with user research, as needed
- Documenting the final approach
- Releasing it through the system
How we improve the system
We continuously strengthen Anvil2 through:- Regular audits
- Accessibility reviews
- Recurring feedback from office hours
- Contribution requests
- Release retrospectives
- Usage metrics across design and code
- Quarterly workflow immersion