MacCMS v10 (magicblack/maccms10): a PHP video CMS you install with install.php
MacCMS v10 (Apple CMS v10) — an open-source PHP CMS for video, articles, manga, images and site navigation.
At a glance
- What is it?
- MacCMS v10 is an open-source PHP and MySQL content management system for video, articles, manga, images and site navigation. It runs on the ThinkPHP 5.x kernel, separates templates from backend code, and ships with a browser installer.
- Who is it for?
- Adopt MacCMS v10 if you run a PHP and MySQL host and want a video or manga catalogue with a browser installer and templates you can edit in plain HTML. Do not adopt it if you need a documented public API, a formal upgrade path, or a licence you can read without ambiguity.
- Can I use it commercially?
- Check first. The repository uses a licence we do not classify automatically, so read its LICENSE file before any commercial use.
- Is it still maintained?
- Yes. The repository last received commits 11 days ago.
- What is it written in?
- Mainly PHP, according to GitHub's language statistics.
Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.
Star history
- magicblack/maccms102,928 ★ · +39
| Repository | 2026-09-30 | 2026-11-15 |
|---|---|---|
| magicblack/maccms10 | 2.9k | 2.9k |
39 Stars in the last 46 days, measured from the daily GitHub snapshot. Compare with other projects
Editorial analysis
What MacCMS v10 is for, and who actually needs it
MacCMS v10 targets a specific kind of site: a catalogue. The repository description calls it an open-source PHP CMS for video, articles, manga, images and site navigation, and the README describes a PHP and MySQL site-building system. That list is the product definition. If your content is a set of items such as videos, articles, manga or images, the product is already aimed at you. If your content is something else, you will be fighting the schema.
The audience is the individual site operator. The README repeatedly frames decisions around the station director (站长), and the stated goal is that an ordinary virtual host is enough to build the site, keeping cost low. That is a real constraint, not marketing filler: shared hosting with PHP and MySQL is a different deployment target from a container platform, and it shapes everything from the installer to the caching advice.
It is not aimed at application developers who want a content API to build a front end against. The repository has api.php at the top level, so check what it exposes before relying on it.
ThinkPHP 5.x kernel and the template split
The README states that v10 is built on the tp5.x kernel and extends the template processing engine so that the backend program and the HTML templates are separated. In practice this means the PHP application and the theme files live apart, and the repository layout reflects that: application/ holds the code, template/ holds the templates, and vendor/ and thinkphp/ hold dependencies and the framework itself.
The stated benefit is that designers and programmers can work without interfering with each other, and that plain HTML knowledge is enough to produce a personalised site. That claim is worth taking literally: the templating is tag-based, and the README mentions built-in tags and a custom function tag interface. So a theme author writes HTML with tags in it rather than writing PHP. The trade-off is that heavy logic in a template is not the intended path, and complex conditional layouts end up expressed through tags rather than normal code.
The README also mentions a custom collection (采集) function for pulling content in. It describes it only as powerful. If automated ingestion is central to your plan, test its behaviour before committing.
Installing MacCMS v10 on a PHP and MySQL host
The repository contains install.php at the top level, and the README says the program runs in a PHP and MySQL environment. So the install path is a browser-driven one rather than a command-line one. Upload the files to the document root, then open the installer in a browser. Check composer.json in the repository root for the dependency constraints before you pick a host.
Once the installer finishes, the two entry points named in the repository layout are the front site at index.php and the backend at admin.php. The README describes the backend module as clear at a glance and simple to operate. Leaving a reachable installer on a live site is a common mistake, so confirm install.php is removed or unreachable before pointing a domain at it.
For a first real use, create one category and one entry, then open the corresponding theme file under template/ and change a heading in plain HTML. That single edit exercises the whole chain: the admin writes to MySQL, the ThinkPHP layer resolves the route, the template engine renders your tag markup. If the heading changes on the front page, the separation the README describes is working as advertised.
The licence is the first thing to resolve
The repository metadata reports the licence as NOASSERTION, which means the automated classifier could not map the LICENSE file to a known identifier. There is a LICENSE file in the repository root, so the terms exist; they simply are not machine-readable in the form the tooling expects. That is a practical problem, not a legal one: you cannot answer a compliance question from the metadata alone.
Read the LICENSE file directly and decide whether its terms fit how you intend to run the site. Do not infer the terms from the project's open-source framing, and do not treat the presence of a LICENSE file as confirmation of any particular licence.
Where MacCMS v10 breaks down
The most concrete limitation is documentation. The README is a promotional introduction in several languages, not a manual. There is also a 说明文档 (documentation) directory in the repository that is worth checking.
The second limitation is the release cadence. The most recent releases are v2026.1000.4056 on 2026-08-19, v2026.1000.4055 on 2026-07-31 and v2026.1000.4054 on 2026-07-17, and the last push to the repository was on 2026-10-14. Version numbers in this format carry no clear semantic meaning about breaking changes. If you modify core files, you own the merge on every release.
The third is the framework generation. The README states the kernel is tp5.x. ThinkPHP 5.x is an older line, and that matters if your organisation has a policy about supported framework branches.
Finally, this is the wrong tool when you need a headless CMS. If your front end is a JavaScript application consuming JSON, the template-tag model is the opposite of what you want..
Alternatives and the real difference in approach
The obvious comparison is WordPress. Both are PHP and MySQL, both install through a browser, and both separate themes from backend code. The difference is the data model. WordPress is built around posts, pages and taxonomies, and a video catalogue is assembled on top of that with plugins and custom post types. MacCMS v10 starts from the catalogue: video, articles, manga, images and navigation are first-class content types in the product itself, and the README presents the built-in tag system as the way themes read them. If your site is a catalogue, the schema is already there. If your site is a blog with a video section, WordPress fits without a plugin layer.
A second comparison is a static site generator. That approach removes the database and the admin interface entirely and gives you a build step and version control for content. MacCMS v10 goes the other way: MySQL storage, a browser admin, and the README's claim that an ordinary virtual host is enough. Choose based on who edits the content. A static generator suits an editor who is comfortable with git. MacCMS v10 suits an operator who wants a login form and a category tree.
Upgrade cost and what to check before you commit
Upgrades are the ongoing cost. Three releases shipped between 2026-07-17 and 2026-08-19, roughly every two to three weeks, and the last push was on 2026-10-14. At that cadence, a fork of the core becomes expensive quickly. The cheap discipline is to keep your changes in template/ and leave application/ and thinkphp/ untouched, so an upgrade is a file replacement rather than a merge.
Take a MySQL dump before any upgrade and verify the site afterwards.
Before adopting, verify three things in this order. Read the LICENSE file. Check the PHP and extension requirements in composer.json against your host. Then confirm that install.php is removed or unreachable once setup is complete..
Editorial conclusion
Adopt MacCMS v10 if you run a PHP and MySQL host and want a video or manga catalogue with a browser installer and templates you can edit in plain HTML. Do not adopt it if you need a documented public API, a formal upgrade path, or a licence you can read without ambiguity. Before committing, check the LICENSE file in the repository root, confirm your PHP version against composer.json, and test one template edit end to end on a throwaway database.
Frequently asked questions
What is MacCMS v10?
It is an open-source PHP and MySQL content management system for video, articles, manga, images and site navigation, built on the ThinkPHP 5.x kernel. The README describes it as a fast site-building system that separates backend code from HTML templates.
How do I install MacCMS v10?
Upload the repository contents to a PHP and MySQL host and open install.php in a browser. The front site is served by index.php and the backend by admin.php.
Does MacCMS v10 have an English interface?
The README itself is published in several languages, including English. The repository does not state whether the admin interface or the default templates are translated, so check the template files under template/ before assuming an English front end.
Can I use MacCMS v10 to build a manga or image site?
The README lists manga, images and site navigation alongside video and articles as content types the system covers.
What licence is MacCMS v10 released under?
The repository metadata reports the licence as NOASSERTION, meaning the LICENSE file in the repository root could not be matched to a standard identifier. Read that file directly to determine the actual terms.
Official sources
Add this badge to your README
If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.
[](https://hysenlabs.com/projects/magicblack-maccms10)Star history chart for your README
[](https://hysenlabs.com/projects/magicblack-maccms10)Was this useful?