Ghostfolio is an open-source wealth management application that enables individuals to track and analyze their personal investment portfolios. It supports multiple asset classes (stocks, ETFs, cryptocurrencies, bonds, real estate) and integrates with numerous financial data providers (Yahoo Finance, CoinGecko, Alpha Vantage, etc.) to automatically fetch market prices, historical data, and asset profiles. The system provides comprehensive portfolio performance calculations (ROAI, TWR, MWR), benchmark comparisons, dividend tracking, and a rule-based X-ray analysis for risk assessment (currency/asset class/regional cluster risk, emergency fund coverage, fee ratios). It also includes a FIRE calculator, watchlist, and import/export functionality for activities. The architecture follows a full-stack monorepo pattern using Nx, with an Angular 22 frontend (standalone components, Material Design, Chart.js) and a NestJS 11 backend (Prisma ORM with PostgreSQL, Redis caching, Bull queues for background data gathering). Authentication supports JWT, OAuth (Google, OIDC), API keys, and WebAuthn passkeys. The system is self-hostable via Docker Compose and includes a premium subscription tier managed through Stripe. The codebase is modular with shared libraries (`libs/common` for DTOs, interfaces, utilities; `libs/ui` for reusable Angular components) and a clear separation of concerns across API modules, services, and queue processors. Key highlights include a pluggable data provider abstraction, an abstract portfolio calculator with caching and retry logic, a comprehensive permission and scope system for fine-grained access control, and a rich UI component library with Storybook documentation. The project is actively maintained with frequent releases, extensive Prisma migrations, and a large test suite for portfolio calculations and import validation. While the codebase shows some technical drift (proliferation of environment variables, deprecated endpoints, and multiple data provider integrations), the overall engineering quality is strong, with well-structured modules and reusable patterns that could be extracted for other financial applications.
HugoBlox Kit is a modular static site framework built on Hugo, providing a block-based page builder for academic, portfolio, documentation, and marketing websites. It uses Hugo's template system with Preact for interactive components, Tailwind CSS v4 for styling, and supports various third-party services (analytics, comments, search). The architecture is a monorepo with core modules (blox, analytics, slides, integrations) and multiple starter templates. Key entry points include the block system (blox/), layouts, shortcodes, and partials. Data flows from Markdown content and YAML configuration through Hugo's build pipeline, with client-side hydration via Preact. External dependencies include Hugo Extended, Node.js, pnpm, and various CDN-hosted libraries (Reveal.js, Mermaid, KaTeX, etc.). The framework is heavily oriented toward academic and research use cases, with features like BibTeX import, publication pages, and author profiles, but also serves general-purpose sites like SaaS landing pages and documentation.
This repository is a minimalist CV (resume) web application built with Next.js 16, React 19, TypeScript, and Tailwind CSS. It serves as a personal portfolio site that renders resume data from a single TypeScript file into a print-friendly layout. The architecture follows Next.js App Router conventions with server-side rendering and static generation. Key features include a command menu for quick navigation, responsive design, dark mode support, SEO-optimized structured data (JSON-LD), and a production-ready Docker setup. The codebase demonstrates strong engineering practices with clear separation of concerns, reusable UI components, and attention to accessibility and performance.
This is a Hugo theme for building personal digital gardens/static sites. It provides templates, styles, and scripts for a responsive multi-column layout with dark mode, newsletter integration, portfolio showcase, and social media links. The architecture follows Hugo's theme structure with layouts in /layouts, assets in /assets, and an example site for demonstration. Key entry points are the base template (_default/baseof.html) and section-specific templates (articles, portfolio, stack). Data flows involve rendering Hugo content (Markdown) via templates, consuming site config (menus, params), and optional data files (stack.json). External dependencies include Hugo (>=0.121.1), Tailwind CSS, and optional services like Google Analytics and newsletter providers (Buttondown, Substack, Revue).
Dante is a static site generator theme for Astro.js, designed for single-author blogs and portfolios. It provides a complete, production-ready setup with dark/light mode, responsive design, SEO metadata, RSS feed, sitemap, pagination, and a subscription form. The theme is built with Tailwind CSS v4 and uses Astro's content collections for Markdown-based blog posts, pages, and projects. Configuration is centralized in a single TypeScript file. The architecture follows Astro's SSG model with view transitions for a SPA-like experience. The codebase is well-structured, with reusable components and utility functions. It is a hybrid of a theme and a starter template, not a library or service.
This repository is a Hugo-based starter template for building an academic CV website, part of the HugoBlox ecosystem. It provides pre-configured project structure, sample content (blog posts, publications, projects, courses, events, slides), and CI/CD workflows for deployment to GitHub Pages or Netlify. The codebase is primarily configuration (Hugo, YAML, Go modules, npm packages) and Markdown content, with minimal custom layout code (a single partial for a GitHub button). Its primary value is as a boilerplate for researchers and academics to quickly spin up a personal portfolio site. While it contains no complex application logic, it demonstrates solid engineering practices through well-structured configuration, modern build tooling (Tailwind CSS v4, Pagefind search), and reusable CI/CD patterns.
This repository is a personal portfolio website built with Next.js 14, React, and TypeScript. It features a blog section with MDX-powered articles sourced via Contentlayer, a projects showcase, and a responsive UI built with Chakra UI. The application uses static site generation (SSG) for optimal performance and includes client-side search functionality for articles and projects. Key architectural elements include the Next.js app router, file-based routing, and a modular component structure separating layouts, UI components, and data utilities. The site implements modern web development practices such as dark/light theme support, image optimization with blur placeholders, analytics integration (Vercel and Google Analytics), and error monitoring via Highlight. Content is sourced from MDX files in the data/articles directory and static JSON files for projects and publications. The build process leverages Next.js's incremental static regeneration (ISR) capabilities through Contentlayer, ensuring content updates without full rebuilds. Notable reusable components include a custom BlurImage component that enhances perceived performance by showing a blurred placeholder during image loading, and a Callout component for styling informational, warning, and error messages in MDX content. Both components are decoupled from specific business logic and demonstrate solid encapsulation patterns suitable for extraction into other projects.
This repository is a modern, minimalist portfolio template built with Astro and Tailwind CSS v4. It provides a single-page static site with sections for hero, about, projects, experience, education, and footer, all driven by a centralized configuration file (`src/config.ts`). The architecture is straightforward: Astro components render data from the config, with conditional section visibility based on data presence. The template uses TypeScript for type safety, Tabler Icons for social links, and IBM Plex Mono font. It is designed for easy customization by editing the config file, making it suitable for developers who want a quick, professional portfolio site. The codebase is clean and follows Astro best practices, but it is essentially a boilerplate template with no complex logic or reusable components beyond the template itself. It is not a production application but a static site generator template.
The Kross Hugo theme is a static site generator template designed for creating personal portfolio websites. It provides a complete set of HTML templates, SCSS stylesheets, and JavaScript functionality that transforms Markdown content into responsive, interactive websites using the Hugo static site generator. The theme follows Hugo's conventional directory structure with layouts for templating, assets for styling and scripts, and archetypes for content templates. It integrates modern web technologies including Bootstrap 5 (via Hugo module), Swiper for touch-enabled sliders, Shuffle for filtering and masonry layouts, and custom JavaScript for UI enhancements like sticky navigation, parallax effects, and attribute-driven styling. The theme emphasizes performance with built-in optimization for Google Page Speed scores. While much of the code is theme-specific, the implementation contains several reusable patterns that demonstrate thoughtful frontend development. Notably, the mouseParallax function in assets/js/script.js provides a self-contained implementation of mouse-followed parallax effects that could be extracted and reused in other projects with minimal modification. The theme also showcases good practices in SCSS architecture with modular styling, responsive typography scaling, and reusable mixin patterns. The project shows evidence of ongoing maintenance with compatibility for recent Hugo versions and configuration for modern deployment platforms like Netlify and Vercel. It addresses common requirements for personal websites including contact forms, social media integration, client showcases, and testimonial sliders, making it a practical solution for developers seeking to quickly deploy professional portfolio sites.
This repository is a design portfolio and technical showcase for a solar photovoltaic GIS prospecting and forecasting platform. It does not contain a runnable application; instead, it provides architectural documentation (docs/ARCHITECTURE.md, docs/MODULES.md, docs/AI_FORECASTING.md) and three well-crafted code snippets that demonstrate the engineering patterns behind map-based lead identification, AI roof detection service, and PV generation forecasting. The snippets illustrate professional-level software design: input validation, security boundaries, model routing, fallback strategies, and business logic normalization. The repository serves as a reference for architects and engineers evaluating similar systems, but it is explicitly non-reusable for commercial purposes due to the license restrictions.
This repository is a curated list of GitHub profile README examples, tools, articles, and tutorials. It does not contain any application code or data pipelines. The primary content is a single README.md file with categorized links. The repository includes GitHub issue templates, a contribution guide, and a basic CI workflow for code formatting. It serves as a reference resource for developers looking to enhance their GitHub profiles. The high number of open issues (706) suggests the list may not be actively maintained, and many links could be outdated.
This repository is a personal portfolio and link aggregation page for Anton Babenko, a well-known figure in the Terraform and AWS DevOps community. It contains no source code, application logic, or data pipelines. The sole content is a README.md file that lists links to the author's social media profiles, media projects (YouTube channel, newsletter), major open-source projects (terraform-aws-modules, pre-commit-terraform, serverless.tf, compliance.tf), utilities, and abandoned projects. It serves as a central directory for discovering the author's work, but it is not a functional software repository. There are no executable files, tests, configuration files, or any code that can be run or reused. The repository is essentially a static documentation page with no technical depth.