Guides & Package Docs | Uptime Watcher

📄️ 📡 API & IPC Documentation

Interface Reference: Comprehensive guide to IPC communication, events, and API patterns in Uptime Watcher.

📄️ 🚀 Developer Quick Start Guide

Fast Track: Get up and running with Uptime Watcher development in minutes.

📄️ Chrome DevTools Snippets for Testing

This document contains useful Chrome DevTools snippets for testing the Uptime Watcher application.

📄️ 📚 Documentation Index

Navigation Hub: Complete guide to all Uptime Watcher documentation with quick links and descriptions.

📄️ Documentation Style Guide

This guide establishes consistent formatting and content standards for all Markdown documentation in the Uptime Watcher project.

📄️ Docusaurus Documentation Setup Guide

Overview

📄️ 🛠️ Environment Setup Guide

Complete Setup: Comprehensive guide for setting up the perfect development environment for Uptime Watcher.

This guide provides comprehensive documentation for the TypedEventBus-based event system in Uptime Watcher, covering event-driven architecture patterns, automatic metadata injection, IPC forwarding, and real-time communication between backend and frontend.

📄️ Enhanced Monitoring System Implementation Complete - Uptime Watcher

✅ Migration Status: COMPLETED

📄️ IPC Automation Workflow

Last updated: 2025-10-26 \

📄️ Logger Migration Report - Comprehensive Analysis and Strategic Implementation

🎯 Executive Summary

📄️ Monitoring State Race Condition Solution Plan

✅ SOLUTION FULLY IMPLEMENTED

📄️ Uptime Monitoring System - New Monitor Type Implementation Guide

Last reviewed: September 30, 2025

📄️ 📁 Documentation Organization Summary

Clean Slate: The docs folder has been reorganized to focus on current, actionable documentation while preserving historical materials in an archive.

📄️ Guides documentation

This directory contains comprehensive guides for developers, contributors, and users of the Uptime Watcher application.

📄️ Renderer Integration Guide

Audience: Teams integrating custom renderer extensions, white-label shells, or third-party dashboards with Uptime Watcher 17.4.0 and later.

📄️ Storybook Vitest Component Testing

This guide explains how the project runs browser-driven tests against Storybook stories using the @storybook/addon-vitest integration.

📄️ Style & Layout Guide

This guide documents the shared styling primitives that keep the renderer consistent. Follow these practices whenever you add screens, modals, or high-level layout primitives.

📄️ TECHNOLOGY_EVOLUTION

🔄 Technology Evolution Guide

📄️ Testing and Coverage Setup

This project uses Vitest for testing with separate configurations for frontend (React), backend (Electron), and shared utilities, integrated with comprehensive mocking strategies and coverage reporting.

📄️ React Component Testing Methodology

Overview

📄️ 🔧 TroubleSolutions:

Prevention: The postbuild script should handle this automatically, but sometimes fails in certain environments.uide

📄️ Type-fest Integration Patterns

This document provides comprehensive patterns for integrating type-fest utilities consistently across the Uptime-Watcher codebase. These patterns ensure type safety, better developer experience, and maintainable code.

📄️ UI Feature Development Guide

This document provides comprehensive guidelines for adding and modifying UI features in the Uptime Watcher application, based on lessons learned from implementing the site monitoring functionality and modal improvements.

📄️ Vite Performance Profiling and Optimization Guide

This document outlines how to use the performance profiling scripts and warmup configuration for the Uptime Watcher application.

📄️ Zustand Store Pattern Decision Guide

This guide helps developers choose the appropriate Zustand store pattern based on store complexity and requirements, reflecting the current modular composition architecture.

📄️ Validation Strategy

The application enforces data quality through a layered validation pipeline. Each layer owns a clearly defined set of responsibilities so that validation code stays maintainable, testable, and consistent across domains.