Skip to content

content(blog): DRAFT — "Gebaut, nicht gewollt" (evig platform vs Revamp-IT legacy) - #250

Merged
catomean merged 2 commits into
mainfrom
blog/evig-vs-legacy-comparison
Jul 28, 2026
Merged

content(blog): DRAFT — "Gebaut, nicht gewollt" (evig platform vs Revamp-IT legacy)#250
catomean merged 2 commits into
mainfrom
blog/evig-vs-legacy-comparison

Conversation

@catomean

Copy link
Copy Markdown
Collaborator

What

A draft blog post comparing the evig platform against Revamp-IT's legacy stack, per request. Non-public draftpublished: false + audience: author (super-admins only) + visibility: unlisted. It does not appear in the public blog, RSS, or listings, and merging this PR would not expose it. Review the prose here; to go live, flip published: true / audience: public / visibility: public.

Framing: "rejection, stated cleanly" (your pick)

  • States plainly that the platform was built and Revamp-IT chose to stay on its legacy stack — Joomla (revamp-it.ch) + Shopware + Kivitendo (Perl, no real API) — and that evig believes the automated path is better and goes it alone.
  • Wins on merit: a factual old-vs-new side-by-side table, real scale numbers, the modern stack, and the roadmap (access to intelligence, robotics, shared-subscription/pooled financing, open R&D).
  • No personal or political attacks, no naming of individuals, no profanity — deliberately excluded (defamation/reputation risk; it would undercut foundation outreach).

Notes

  • DE only for now — translations follow once you approve the copy (DE is canonical + the fallback).
  • Reuses already-committed screenshots (/blog/showcase-revampit-*.png).
  • There's an existing published post (die-revamp-it-plattform.md) telling the "three systems → one platform" story from the old framing; this new post is the sharper evig-voice comparison + roadmap. Decide whether both coexist or the old one is retired.

Open decisions for you

  • Sharpen tone further? (I kept it confident-but-respectful.)
  • Publish target audience (public vs team) and timing.

🤖 Generated with Claude Code

catomean and others added 2 commits July 28, 2026 09:18
…p-IT legacy stack (DRAFT, non-public)

A comparison + roadmap post per George's request: makes clear evig's platform was
built and Revamp-IT chose to stay on its legacy stack (Joomla + Shopware +
Kivitendo/Perl, no API), lays out what was built and the roadmap (access to
intelligence, robotics, financing models, open R&D). "Rejection stated cleanly":
factual, respectful, wins on merit — NO personal/political attacks, no naming of
individuals.

Non-public by design: published:false + audience:author (super-admins only) +
visibility:unlisted. To publish: flip to published:true / audience:public /
visibility:public. DE only for now (translations follow once copy is approved).

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
…le upcycling E2E

- Publish the evig-vs-legacy comparison post: published:true / audience:public /
  visibility:public, drop the draft banner. DE canonical + en/fr/es/it/ja/ko
  translations (title/excerpt translated, tables + image paths + brand/tech names
  preserved).
- Fix red CI: drop the /projects/upcycling route #116 entries from the dual-persona
  E2E route matrix. Those pages were intentionally removed with the /projects purge
  (commit 10c1b8a) and now 404; the smoke test kept asserting them. (The upcycling
  CONFIG/assets are left intact — revive-or-retire is a separate call.)

Verified: tsc clean, eslint clean on the E2E helper, all 7 post files valid
frontmatter + published:true + tables + images.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@catomean
catomean marked this pull request as ready for review July 28, 2026 07:45
@catomean
catomean merged commit b6af5a2 into main Jul 28, 2026
7 checks passed
@catomean
catomean deleted the blog/evig-vs-legacy-comparison branch July 28, 2026 08:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant