varharrie/varharrie.github.io

:blue_book: Personal blog site based on github issues.

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 2 hours ago
Added to GitGenius on September 18th, 2026
Created on December 7th, 2016
Open Issues & Pull Requests: 41 (+0)
GitHub issues: Enabled
Number of forks: 540
Total Stargazers: 3,678 (+0)
Total Subscribers: 125 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 0.2 hours
Mean response time: 103.2 days
90th percentile: 412.4 days
Tracked items: 4

Most active contributors

Sign in to see contributor activity.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 5
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 727 days
Stale 30+ days: 5
Stale 90+ days: 5

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • Styles (2)
  • Javascript (1)
  • Vue (1)

Most active issues this week

Sign in to see which issues are moving.

Detailed Description

varharrie.github.io is a personal blog site that uses GitHub issues as its content source.

The project solves the problem of maintaining a blog without needing a dedicated backend server by leveraging GitHub's issue tracking system as a content management layer. It builds a static site from issues, allowing developers to write and publish posts through GitHub's familiar interface while keeping infrastructure minimal.

This approach suits developers who already use GitHub and want to avoid server maintenance overhead. The tool works best for those comfortable managing content through issues and who value simplicity over a traditional CMS. It includes built-in support for dark theme, internationalization, and a code playground integration, making it suitable for technical blogs that need to showcase code examples. The project is written in TypeScript and built with React, so it appeals to developers in that ecosystem.

Development activity shows consistent engagement with the codebase. The project maintains an active commit history demonstrating ongoing refinement and feature work. Pull request activity indicates collaborative development with external contributions being reviewed and integrated. Issue tracking shows the maintainer actively responds to and manages reported problems and feature requests, suggesting responsive stewardship of the project.