RADFish Technical Decision Log
This section provides justification for the technologies and frameworks we chose for RADFish. Most pages include "Why we chose this", "Trade-offs", and "Alternatives" sections. These demonstrate pros, cons, and other options that were considered, respectively.
For more information about this section, read the statement of purpose.
📄️ Purpose
Provides clarity around technical decisions
📄️ Trussworks Component Library
Adherence to US Web Design Standards
📄️ Mock Service Worker
Required for offline functionality
📄️ Prettier and ESLint
Ensures consistent code quality and style
📄️ JavaScript with JSDoc
Accessible and easy to adopt
📄️ Dexie for Offline Data
Simplifies working with IndexedDB
📄️ Workbox
Service worker management for improved caching
📄️ TanStack for State Management
Offers flexible state management