# 6 minutes, 50 forks: how a "Go WordPress" got its stars, and how it lost them · GitHub open source projects

> Source: https://stringers.io/en/github/gh_gopherium__gophenberg.html (Stringers / 什么值得做, generated 2026-11-08)
> Stringers answers one question every day: what small product can one or two people build in a few months and actually make money from. Numbers come from 15 databases we collect daily, each with source and date.
> For agents: these verdicts and the underlying databases (verified revenue, App Store / Google Play charts, ad libraries, GitHub, Product Hunt…) are queryable live over MCP — tools today / hot / products / directions / direction / data. Setup: https://github.com/komako-workshop/stringers (the user logs in at stringers.io → "配置 agent" to get a personal URL). Site index: https://stringers.io/llms.txt

> There was no real traction: two star surges (mid-October, +284 in 4 days, and a single day of +276 on 11-02) matched batches of forks and stars from newly registered accounts, both later wiped by GitHub, and nobody on Hacker News, X, or the WordPress community discussed it.

[GitHub open-source project](https://stringers.io/en/github/index.md) · written 11-6

gopherium/gophenberg · gopherium

# 6 minutes, 50 forks: how a "Go WordPress" got its stars, and how it lost them

**What it is** A self-hosted content management system. Writers use WordPress's Gutenberg editor in the admin, the backend replaces PHP with Go and PostgreSQL, and the frontend themes are built with Astro.

**Why it blew up** It never really did. Two star spikes (October: +284 over 4 days, and +276 in a single day on 11-02) lined up with forks and stars from freshly registered accounts. GitHub later purged them. Hacker News, X, and the WordPress community never discussed it.

**D** **How you could ride it** Don't follow this project. Borrow its topic method instead: pick an open source project everyone on the frontend loves and everyone on the backend hates, connect the frontend to a backend your community prefers, ship a live demo, and on launch day post to Show HN and the relevant language subreddits with a clear explanation.

Grade D: most of its stars were bought, and real demand is unproven. The "post-WordPress" slot is already taken by Cloudflare's EmDash, which has 14k stars, so your odds of earning stars in the same space are slim. Studying its topic method is enough. Few people know about it yet

Data (updated daily) · Repo created 2026-07-19 · 507 stars · 7 days +53

GitHub · stars

Data 2026-10-09 → 2026-11-08 (31 days, 21 observations). Points before 10-28 come from deeply / archive backfill, not every day has one

On Oct 2, 2026, between 1:05 and 1:11 in the afternoon, gopherium/gophenberg on GitHub gained 50 forks in 6 minutes. Click through those accounts and they look nearly identical: registered in mid-September, 0 followers, two repos each, one an empty repo with a random-letter name and the other this fork. A month later, on Nov 2, it gained 276 stars in one day. By Nov 6, GitHub showed 507 stars, down from 772 three days earlier. The project itself is real: one WordPress core contributor built it solo over 110 days. But the stars were pumped up and then mostly purged by GitHub. If you want stars for your own open source project, this case teaches two things: a decent topic idea, and a cautionary tale.

### What it is

Gophenberg is a self-hosted content management system. Its writing interface uses WordPress's Gutenberg block editor directly, the same one anyone who's used recent WordPress will recognize. The backend skips PHP and uses Go plus PostgreSQL. The frontend themes are written in Astro. Plugins are Go packages compiled into the program. The README's first line reads: "A plugin-first CMS. Go backend, React admin, Gutenberg editor."

The author, Manuel Camargo (GitHub handle SirLouen), works at Metricool, a Spanish social media tools company. His WordPress.org profile says he is the current maintainer of the Mail component and a former maintainer of the Post and Post Types components. The repo was created in Jul 19, reached v0.19.0 in Oct 15, and the author made about 2,950 commits himself, averaging more than twenty a day over 110 days. That pace looks like heavy AI-assisted coding (inference). Docs site, Discord, translation platform, and test coverage are all in place. The licensing is handled carefully too: the code he wrote is Apache-2.0, and the bundled WordPress components are GPLv3.

As far as I can find, it's the only project that combines the original Gutenberg editor, a Go backend, and Astro themes.

### The star curve: two spikes, two purges

Daily snapshot stars, compared with GitHub's live count at 11-06 in the afternoon:

| Date | star | fork | What happened |
|---|---|---|---|
| 09-05 | 119 | – | At v0.11.0 |
| 10-02 | – | – | 13:05–13:11 brought in 50 forks |
| 10-12 | 290 | 50 |  |
| 10-13 → 10-16 | 352 → 574 | 51 → 54 | 4 days +284 |
| 10-28 | 453 | 58 | Lost 121 over 11 days |
| 11-02 | 730 | 62 | Single day +276 |
| 11-03 | 772 | 90 | Forks: +28 in one day |
| 11-06 | 507 | 88 | GitHub live count, down 265 over three days |

The Nov 2 batch of forks came from a different kind of account. Their bios read "prs_" followed by a string of numbers. Some were registered at 9:48 that same morning and forked by 10:37. The same batch also forked A2E-Suite, uncut, midgard-app, and even a Genshin cheat panel repo. These are accounts from crowdsourced "star and fork for pay" platforms, where one account takes jobs for several clients at once. Many accounts from both batches can no longer be opened; GitHub banned them.

The Oct 2 batch forked only gophenberg, which suggests it was ordered specifically for this repo. Whether the author ordered it, an outside promoter did, or someone else, I can't tell, and I can't verify it.

There's also indirect evidence. Several other repos under the same organization (AlphOne at 210 stars, godmin 74, gouncer 70, framework 66) gained 0 to 1 stars a day over the same period. If people were really talking about gophenberg, the author's other projects would likely have picked up some of that attention. It also never made GitHub Trending.

### How many people are actually watching

Not many.

- Hacker News searches for "gophenberg" and "gopherium": 0 results. X, past 120 days: 0 posts.

- WordPress media and community outlets (WP Tavern, The Repository, Reddit r/Wordpress) have never written about it. The author's status as a core contributor didn't turn into any reach.

- The only write-up online is a batch-generated page from a mirror site on CSDN, not something someone wrote on purpose.

- 10 people watch the repo. 62% of issues were opened by the author and 24% by a dependency-update bot. Only 6 outside people have opened 11 issues.

- There are 12 real contributors, each with 1 to 18 commits. Many are newcomers who came in through the good first issue label during Hacktoberfest in October.

My estimate: the developers really paying attention to it number somewhere between a few dozen and a hundred or two (estimate), and a lot of the 507 stars are padding. At least 78 of the 88 forks were bought, so they can't be used as evidence that anyone is deploying it.

### The "post-WordPress" slot is already taken

| Project | Scale (GitHub stars, 11-06) | How it differs from Gophenberg |
|---|---|---|
| EmDash(Cloudflare) | 14,199, now at 1.0 | Released 2026-04-01. Also calls itself "the successor to WordPress" and also uses Astro. It's a TypeScript full stack running on Cloudflare Workers, with plugins in a sandbox, and it doesn't use Gutenberg. InfoQ and CMSWire have both covered it. |
| WordPress / Gutenberg | Gutenberg 11,787; WordPress runs about 40% of websites | Gophenberg takes its editor |
| Laraberg | No updates since 1,371,2024-12 | Gutenberg ported into Laravel, but only the editor component |
| Automattic isolated-block-editor | 412 | A package the official team split out. It's just the editor |
| ClassicPress | 864 | A WordPress fork that opposes Gutenberg, so it's going the opposite direction |
| Ponzu | Mostly unmaintained since 5,759 | A Go CMS with no rich text editor |
| PocketBase | 61,608 | A single-file Go backend, not a CMS. Go developers often use it to build their own content sites |
| Payload / Directus / Strapi / Ghost | 38k–56k | Mature headless CMSs and blogging platforms, with a much larger ecosystem |

The topic "WordPress is too old and PHP is too heavy, time to move on" was already claimed in April by Cloudflare's EmDash. Gophenberg's combination is genuinely unique, but it has no voice in that conversation, and its stars didn't come from the combination.

### What to copy and what to skip

**Copy the topic choice.** Take the part of a mature open source project that people use and like most (here, the Gutenberg editor) and attach it to the backend of a new stack. Writers don't have to learn anything new, and developers get to leave a stack they didn't want to touch. One person with AI in 110 days reached v0.19, which shows that "swap a beloved frontend onto a new backend" is now something one person can build.

**Skip the distribution.** It never posted to Show HN, never went to r/golang, never pitched WordPress-world media, and never used its author's "WordPress core maintainer" status to tell the story. The stars were bought. They were purged twice, and anyone can look up the drop curve. For a CMS that wants to win users on its maintainer's reputation, that hurts more than a low star count would.

### If it were you

**One verdict:** Don't follow this project itself. A "Go WordPress" has neither proven demand nor room next to EmDash's shadow. The only thing worth taking is the topic method: borrow a beloved frontend and swap the backend.

**Best suited for:** longtime contributors to a large open source project who know which part people love most and which they complain about most, who can use coding agents for large rewrites, and who have some standing in a developer community (Go, Rust, or a particular framework scene).

**Who it's not for:** If you want to go head-to-head as "the next WordPress", EmDash has Cloudflare behind it and 14k stars, and you won't win that fight. If you have no distribution channel and plan to start by buying stars, know that GitHub cleans them up fast, and the cleanup curve stays on the chart.

**How to do it:**

1. Pick an open-source project that "everyone on the frontend loves and everyone on the backend hates". Ideally the frontend is already split into standalone packages (Gutenberg ships an official standalone editor package).

2. Swap in the backend your community prefers: Go, Rust, or single-binary deployment. Put "the editing experience you know, runs as one binary" in the first screen of the README.

3. Ship a live demo where people can click in and write a post right away. Don't make them install Docker and Postgres first.

**How to get users:** On launch day, post once on Show HN and once in the relevant language subreddits. Use a one-line comparison in the title, e.g. "Gutenberg editor, no PHP: a single Go binary". If you're a contributor to the original project, say so in the first paragraph and pitch the media covering that project's circle. Use events like Hacktoberfest to recruit contributors, but don't expect them to bring stars.

**When is "before":** No rush. This kind of topic doesn't ride a trend, so doing it solidly matters more than being early. But on the specific "post-WordPress" angle, every release EmDash ships leaves less room.

**What would show I'm wrong:** If Gophenberg keeps climbing steadily for three months after the star-buying stopped, or if people in Hacker News or the WordPress community start writing about it on their own, that would mean "original Gutenberg + non-PHP backend" has real demand on its own. Then it and its followers would be worth a second look.

[GitHub repo ↗](https://github.com/gopherium/gophenberg)

**Research notes: competitor table, acquisition evidence, full research report**

Competitors

| Name | Where | Launched | Scale | How it differs from this one |
|---|---|---|---|---|
| EmDash(Cloudflare) | Open source | 2026-04-01 | 14.2k stars, reached 1.0; covered by InfoQ/CMSWire | Also pitches itself as a "WordPress successor" and uses Astro, but in TypeScript, runs on Workers, sandboxes plugins, and doesn't use Gutenberg. Backed by a big company. |
| WordPress / Gutenberg | Open source | 2003 / 2017 | gutenberg 11.8k stars; WP runs about 4 of all websites | Gophenberg takes its editor and swaps the PHP backend for Go |
| Laraberg | Open source | 2019 | 1.4k stars, no updates for 2024-12 | Just drops the Gutenberg editor into Laravel. Not a full CMS |
| Automattic isolated-block-editor | Open source | 2021 | 412 star | Official standalone editor package. Editor only |
| Ponzu | Open source | 2016 | 5.8k stars, essentially unmaintained | Headless CMS written in Go. No rich editor |
| PocketBase | Open source | 2022 | 61.6k star | Single-file Go backend. Not a CMS |
| Payload / Directus / Strapi / Ghost | Open source | 2013-2021 | 38k-56k star | Mature JS/TS headless CMS and blogging stacks with a much bigger ecosystem |

Where users come from

- **Confirmed** **Fork/star farming (account warming)** : 2026-10-02 13:05-13:11 brought in 50 forks. The accounts were registered 9-10~9-23, have 0 followers and 2 repos, use random-word names, and only forked this one repo. Several are already 404.

- **Confirmed** **Crowdsourced star/fork task platform** : 11-02 brought in 28 forks in one day. The account bios are prs_xxxxxx-style IDs, and the same accounts also forked unrelated repos like A2E-Suite, uncut, and a Genshin cheat panel. Stars that day: +276.

- Inferred **WordPress core contributor identity** : Credited in the README, and the WP.org profile lists them as Mail component maintainer. But no WP community media or community has covered it.

- Inferred **Hacktoberfest/good first issue** : 12 external contributors, with 1-18 commits each.

- Inferred **HN/Reddit/X/media** : HN Algolia, x-radar, and Jina search all returned 0.

## gopherium/gophenberg: a "WordPress backend" written in Go. The stars were bought.

> 2026-11-06 research. Sources: GitHub API (live), our github database repo_day (since 2026-10-09), Jina search, HN Algolia, x-radar.

### One line

Gophenberg is a self-hosted CMS built solo by WordPress core contributor Manuel "SirLouen" Camargo. The backend is a rewrite in Go + PostgreSQL, the admin reuses WordPress's Gutenberg block editor and the WPDS design system, and the frontend themes use Astro. **It never really took off** : it never made GitHub Trending, and there's no discussion on HN, Reddit, X, or in media. The two spikes on the data card (10-13~10-16 up 284,11-02, and a single day up 276) both match bulk fake-account activity, and GitHub then removed a large batch. Stars fell from 772 to 507 (2026-11-06 live).

### 1. How the stars came: two rounds of inflation + two rounds of cleanup

#### Star curve (our repo_day database, checked against live GitHub counts)

| Date | stars | forks | Notes |
|---|---|---|---|
| 09-05 | 119 | – | deps.dev records (the found field on the data card) |
| 10-09~10-12 | 299→290 | 50 | Already losing stars |
| 10-13~10-16 | 352→487→515→574 | 51→54 | First spike, +284 in 4 days |
| 10-28 | 453 | 58 | -121 within 11 days, cleaned up |
| 11-02 | 730 | 62 | Second spike, +276 in one day |
| 11-03 | 772 | 90 | Another +42; forks +28 in one day |
| 11-06 | 764 (database) / **507 (live GitHub API)** | 88 | Second round cleaned up, -265 |

Other repos under the same org (AlphOne 210, godmin 74, gouncer 70, framework 66) were each getting 0~1 stars a day over the same period, with no lift at all. If people were actually talking about gophenberg, the author's sister projects would usually catch some of it.

#### Evidence from the fork list (GitHub API `repos/gopherium/gophenberg/forks`, first 100)

- **2026-10-02 forks in 13:05–13:11,6 minutes 50 in that window** . Sampled accounts (desiretraderportal, GrandCoral64, TankManagerRetake, GlowCenterEnergy, AquaChampion…) were each registered 2026-09-10~09-23, have 0 followers and 2 public repos (one empty repo with a random letter name plus the gophenberg fork), and use random-word-joined usernames. Over a dozen are already 404 (banned). This is a batch of warm-up accounts aimed at this repo specifically, not stray forks from browsing.

- **2026-11-02 一天 28 个 fork** (06:31 起成批出现)。这批账号 bio 是 `prs_xxxxxx` 这种编号(King5442525、abatu22、nahid1272、taufiq2019、L-man04、PrietyAl99……),其中 nahid1272 当天 09:48 注册,10:37 就 fork 了;同一批账号还 fork 了 A2E-Suite、uncut、midgard-app、Genshin-Impact-ESP-Cheats-Panel 等毫不相干的仓库——这是众包「点星/fork 任务」平台的接单号,一个号同时接很多客户的单。也有不少已经 404。

- Only sporadic real forks, spread from late July to early November (0~2 a day).

**Bottom line** : The star count's two jumps both came from inflated stars, and GitHub removed some of them afterward (mid-to-late October -121, November 5~6 -265). GitHub's stargazers API currently returns empty results for every repo (even facebook/react returns 0), so we can't check the accounts that starred it directly. The fork accounts are enough to show the problem. **We can't verify who paid for the stars** (the author, an outsourced promotion firm, or someone else could all be responsible), but the 10-02 accounts forked only this one repo, which suggests they were bought specifically for it.

### 2. Real attention

- HN Algolia exact-match search for "gophenberg" and "gopherium": 0 results.

- x-radar search for "gophenberg" over the last 120 days: 0 results.

- Jina search: only the GitHub page itself and one CSDN "gitblog" auto-generated intro article (blog.csdn.net/gitblog_00195/article/details/153809215, an SEO piece mass-produced by a GitCode mirror site, not written by a person).

- 10 watchers. Of the issue authors, 62/100 are the author and 24 are dependabot. 6 external people filed issues, 11 issues in total.

- Contributors: SirLouen has 2957 commits over 110 days (a clearly heavy AI-assisted pace). There are 12 external contributors, each with 1~18 commits (orshih6 18, dannyward630 9, lux-liang 7…). The repo carries `good first issue` / `help wanted` labels, and a few newcomers sent PRs during October's Hacktoberfest.

- The author's background is real: profiles.wordpress.org/sirlouen lists "Current Mail Component Maintainer – Former Post/Post-Types Component Maintainer". The GitHub account is 2010 years old, has 58 followers, and lists Metricool (Spain) as the employer. But that credibility never turned into spread in the WordPress community: WP Tavern, The Repository, and r/Wordpress on Reddit have no mention of the project.

**Visibility: almost nobody knows about it.** Real followers are probably tens to a hundred or two developers. Most of the 500+ stars are water.

### 3. Competitors

| Name | Where | Launched | Scale (GitHub stars, 2026-11-06) | How it differs from Gophenberg |
|---|---|---|---|---|
| EmDash(Cloudflare) | Open source | 2026-04-01 | 14,199; reached 1.0 | Also calls itself the "spiritual successor to WordPress" and uses Astro. Full TypeScript stack, runs on Workers/D1, sandboxes plugins, and doesn't use Gutenberg. Big-company backing has largely taken the attention in the "post-WordPress" space. |
| WordPress itself / Gutenberg | Open source | 2003 / 2017 | gutenberg 11,787; WP runs about 4 of all websites | Gophenberg just takes its editor and swaps the PHP backend for Go |
| ClassicPress | Open source | 2018 | 864 | A WP fork that goes against Gutenberg. Opposite direction |
| Laraberg | Open source | 2019 | 1,371; no updates for 2024-12 | Drops Gutenberg into Laravel. Just an editor component, not a full CMS |
| Automattic isolated-block-editor | Open source | 2021 | 412 | Official standalone Gutenberg editor package. Editor only |
| Ponzu | Open source | 2016 | 5,759; basically stopped updating | Headless CMS written in Go, no rich editing experience |
| PocketBase | Open source | 2022 | 61,608 | Single-file Go backend, not a CMS, but commonly used by Go devs to self-host content sites |
| Payload / Directus / Strapi / Ghost | Open source | 2013–2021 | 38k–56k | Mature headless CMS / blogging platform with a much bigger ecosystem |

### 4. Growth tactics

| Channel | Evidence | Confirmed |
|---|---|---|
| Fork/star farming (batch-operated accounts) | 10-02 6 minutes, 50 forks, all from accounts newly registered in September with 0 followers, and they only forked this repo | Yes |
| Crowdsourced star/fork task platform | 11-02 28 forks, bios all in the `prs_xxxxxx` numbering format, same batch numbers forking multiple unrelated repos at once; +276 stars that day | Yes |
| GitHub cleanup | 10-17→10-28 -121;11-05→11-06 772→507 | Yes |
| WordPress core contributor credentials | Credited in the README and on WP.org profile, but found no trace of him promoting it in the WP community | No |
| Hacktoberfest / good first issue to attract new contributors | 12 external contributors, good first issue labels | Partial |
| Docs site, Discord, POEditor translations, codecov | README | Yes (infrastructure only, brought no traffic) |
| HN / Reddit / X / media | All 0 | No |

### 5. Differentiation

"Go backend + the original Gutenberg editor + Astro theme + compile-time Go plugins", a combination no one else really offers. The pitch: writers keep the familiar WordPress editor, and developers drop PHP for a single Go binary + Postgres. The license handling is also careful (own code under Apache-2.0, bundled @wordpress/* packages shipped under GPLv3).

But this differentiation is **not** why it gained stars: the two days it really gained were both matched by farmed traffic; and the "post-WordPress" narrative was already taken by Cloudflare's EmDash in 2026 April (14k stars, covered by InfoQ/CMSWire), while Gophenberg had no visibility in that conversation.

### 6. What to borrow

- The product idea is worth borrowing: **take the best-working part of a mature open source project (the Gutenberg editor) and hook it to a backend on a new stack** , so users don't have to relearn anything. One person with AI reached v0.19 in 110 days, which shows this kind of "rewrite someone else's backend" project is now doable.

- A cautionary example: no content distribution at all (no HN, no Show r/golang, no WP Tavern), numbers propped up by star farming, both rounds wiped by GitHub, and the star-drop curve is publicly visible, which damages credibility rather than helping.

- A warning for data recall: "never on Trending + single-day spike + fork counts spiking in batches at the same time" appearing together is basically star farming.

### 7. Uncertain

- Who paid for it (the author himself, a promotion agency, or something else) is unverified.

- Actual deployment numbers are unknown; at least 78 of the 88 forks are farmed, so they can't be treated as evidence that "people are deploying it" (the data card got this judgment wrong in the recall reasoning).

- The stargazers endpoint currently returns empty for all repos, so individual starring accounts can't be checked. We can only infer from fork accounts and star trends.

This article was written by AI from public data and the data we collect daily. Numbers are sourced, and inferences are labeled.