$ show remnawave/panel
This repository contains the official documentation website for the Remnawave proxy management panel. Built with Docusaurus 3.9.x and React 19, it generates a static site that provides installation guides, configuration references, tutorials, and API documentation. The site features a landing page with custom React components (hero section, stats bar, feature highlights, project grids, client cards) and multilingual help articles covering authentication methods, editor templates, and page configurations. A Caddy server serves the built output with routing for the landing page and documentation paths. The repository also includes an awesome-remnawave page indexing community tools (backup scripts, bots, monitoring tools) and a curated list of proxy clients with data-driven card displays. While the actual Remnawave panel backend is hosted separately, this documentation site is a well-structured, actively maintained resource that follows Docusaurus best practices with custom theming, dark mode, and analytics integration.
The LLM identified 3 files worth highlighting for reuse:
A React component that fetches GitHub star counts from the ungh.cc API and caches the result in localStorage with a 1-hour TTL. It gracefully falls back to 'N/A' if the fetch fails, making it resilient to network issues. This self-contained wrapper can be reused in any Docusaurus project to display GitHub Stars without hitting rate limits or requiring a backend.
Renders changelog entries with version headings that automatically generate deep-link anchors using useBrokenLinks(). It supports dev tags and patch lists, making it a reusable component for displaying release notes consistently across documentation pages. The anchor generation pattern ensures every version section is navigable without manual ID assignment.
A typed TypeScript dataset defining metadata for 30+ proxy clients (core, platforms, badges, GitHub repo, download links). Although project-specific, the structure (enum for platforms, badge logic) provides a reusable pattern for any documentation site needing to maintain a curated third-party tool list. The data drives Card and List components, enabling fully dynamic rendering from a single data source.