mindoc-org/mindoc

Golang实现的基于beego框架的接口在线文档管理系统

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 27 minutes ago
Added to GitGenius on September 8th, 2026
Created on April 19th, 2017
Open Issues & Pull Requests: 325 (+0)
GitHub issues: Enabled
Number of forks: 1,973
Total Stargazers: 7,831 (+0)
Total Subscribers: 268 (+0)

Repository Insights (GitGenius)

Most active contributors

Sign in to see contributor activity.

Related repositories by overlapping contributors

No overlapping-contributor repos identified yet.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 44
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 644 days
Stale 30+ days: 43
Stale 90+ days: 41

Recent activity

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

Top labels

  • feature-docker (1)

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

MinDoc is a document management system built with Go and the Beego framework, designed for IT teams to manage API documentation, database dictionaries, and technical manuals.

The system addresses the need for straightforward document storage and sharing within development teams. It evolved from SmartWiki, a PHP-based documentation tool, and was rewritten in Go to simplify deployment for non-technical users. MinDoc provides built-in project management, user administration, and permission controls, allowing teams to organize and share documentation without complex infrastructure requirements.

Teams managing API documentation, database schemas, or internal technical references should consider MinDoc if they want a self-hosted solution with minimal deployment complexity. The tool suits small to medium-sized teams that need basic document organization and access control. It requires Go 1.23.0 or later to build from source, though pre-compiled binaries are available for users without Go development experience. The system runs as a single binary, reducing deployment friction compared to traditional web application stacks.

The project transitioned to community maintenance through a GitHub organization, with an active issue tracker and a development roadmap tracking planned work, in-progress items, and code reviews. The maintainers have established a community communication channel for users and contributors to discuss problems and development direction.