This repository maintains a curated list of developer portfolios in README.md, keeping them sorted alphabetically and validating links. It provides automated tools for sorting entries, detecting broken or parked links, removing emojis from link text, eliminating duplicates, and generating a machine-readable JSON feed (feed.json) from the markdown. The system uses GitHub Actions for continuous link and parking redirect verification, ensuring the portfolio list remains accurate and useful for the developer community.
mermaid-cli is a command-line interface for generating diagrams from Mermaid syntax. It processes input files (.mmd, .md, .markdown) containing Mermaid diagram definitions and outputs SVG, PNG, or PDF files. The architecture centers around a Puppeteer-driven rendering pipeline that launches a headless browser to render Mermaid diagrams via the Mermaid library. Key features include Markdown diagram extraction, configurable theming, CSS injection, icon pack support, and programmable Node.js API. The CLI entry point is src/cli.js, which delegates to the run() and renderMermaid() functions in src/index.js for core functionality. External dependencies include Puppeteer, Mermaid, and various layout engines (ELK, tidy-tree).
Fuwari is a static blog template built with Astro and Tailwind CSS. It generates static HTML from Markdown content with features like light/dark mode, Pagefind-based search, responsive design, and customizable themes. The architecture uses Astro's component-based system with Svelte for interactive elements, Swup for page transitions, and Expressive Code for enhanced code blocks. Content is sourced from Markdown files in src/content/ and processed at build time to generate static assets. Key entry points include page routing files (.astro) and API routes for RSS/robots.txt. The template demonstrates strong engineering practices in its modular component design, effective use of Astro's content collections, and thoughtful implementation of UI interactions.
This is the production codebase for 30secondsofcode.org, a high-traffic content platform serving curated programming articles and code snippets. Despite the repository's historical reputation as a snippet library, the actual code is a full-stack Astro-based static site generator with a sophisticated custom content pipeline. The architecture is a monolithic Node.js application with distinct layers: a custom ORM-like model system (Model, RecordSet), a serializer layer for presentational logic, an adapter layer for page composition, and a comprehensive content ingestion system that transforms Markdown/YAML source files into optimized static HTML pages. The content pipeline is the most architecturally significant component. ContentUtils processes markdown files with custom remark/rehype plugins for code highlighting (Prism/Shiki), table of contents generation, image optimization, and web component injection. The system generates search indices, RSS feeds, sitemaps, and structured data at build time. The search implementation is notably sophisticated, featuring a client-side inverted index with TF-IDF scoring, Porter stemming, and n-gram fuzzy matching—all precomputed during build. The frontend uses Astro components with SCSS, progressive enhancement via web components (table-of-contents, latex-expression, code-tabs), and a sophisticated ranking algorithm for content recommendations. The codebase demonstrates strong separation of concerns with presenters, serializers, and adapters each handling distinct responsibilities. The test suite uses Vitest with factory patterns and fixture-based testing. Maintenance signals are mixed: last commit was June 2026, but the update log from September 2025 explicitly states the creator is taking an indefinite break, issues/PRs are being closed, and content will be sparse. The codebase itself is well-structured with consistent patterns, comprehensive tests, and modern tooling (Astro 6, Node 22, ESM). Dependencies are current. The primary risk is not technical debt but project abandonment—the architecture is sound but the single-maintainer model and explicit break announcement suggest declining activity.
This repository implements a personal knowledge management system centered around LLM-powered content processing. It follows a four-layer architecture: raw/ for immutable source materials, wiki/ for LLM-generated structured knowledge (summaries, concepts, indexes), brainstorming/ for intermediate outputs like chat logs and health reports, and artifacts/ for user-created work. The system processes various input formats (articles, books, PDFs, Facebook exports) through user-triggered commands like /compile and /convert-to-md, which leverage external tools (pandoc, pymupdf) and LLMs to extract insights and build interconnected knowledge networks. The core innovation lies in separating raw consumption from synthesized understanding, allowing users to accumulate source material without immediate processing, then periodically run LLM-driven synthesis to surface patterns across documents. Key workflows include extracting concepts that appear in multiple sources, maintaining bidirectional links between related ideas, and preserving tension between personal experience and external research in concept notes. The system emphasizes provenance tracking, with every synthesized piece linking back to its source via wikilinks. While the system relies on external LLMs and tools for its core functionality, it provides well-defined, reusable components for common data preparation tasks. The Facebook JSON-to-Markdown converter stands out as a robust, standalone script handling encoding normalization, media extraction, and frontmatter generation. The overall design demonstrates thoughtful consideration of knowledge work friction points, though reproducibility is hampered by undocumented environment dependencies and lack of sample data.
Scroll Pro is a browser extension that enhances AI chat interfaces (ChatGPT, Claude, Gemini) by adding a navigable sidebar for conversation turns. It enables users to copy, export (to Markdown, PDF, text, JSON), and navigate chats via a table of contents. The extension operates entirely client-side using React 19.2.0, TypeScript, and Vite, with UI rendered in a Shadow DOM for isolation. Key features include platform-specific DOM parsing, keyboard shortcuts, context menus, and persistent state via browser storage. The architecture centers around a content script entry point that mounts a React app, provider abstractions for each chat platform, and reusable utilities for markdown conversion, scrolling, and file downloads.