Open-Source CMS · ClassicPress

ClassicPress

ClassicPress is a lightweight, community-maintained fork of WordPress 6.2 that removes the Gutenberg block editor in favor of the classic TinyMCE editor. It emphasizes stability, performance, and familiarity for creators who prefer a simpler editing interface and smaller codebase.

Talk to DEV.co Discuss Implementation

Source: GitHub — github.com/ClassicPress/ClassicPress

850

GitHub stars

129

Forks

PHP

Primary language

GPL-2.0

License (OSI-approved)

Key facts

Objective fields from the source. Values we can't verify are shown as “Unknown” rather than guessed.

Field	Value
Repository	ClassicPress/ClassicPress
Owner	ClassicPress
Primary language	PHP
License	GPL-2.0 — OSI-approved
Stars	850
Forks	129
Open issues	37
Latest release	2.7.0+dev (2026-03-25)
Last updated	2026-07-07
Source	https://github.com/ClassicPress/ClassicPress

What ClassicPress is

PHP-based CMS forked from WordPress 6.2, approximately 50% smaller, retaining the classic editor as default while removing block editor and Full Site Editing features. Includes automated CI/CD for coding standards, PHPUnit tests, JavaScript tests, and PHP compatibility validation.

Quickstart

Get the ClassicPress source

Clone the repository and explore it locally.

terminalbash

1git clone https://github.com/ClassicPress/ClassicPress.git2cd ClassicPress3# follow the project's README for install & configuration

Need it deployed, integrated, or customized instead? DEV.co ships production installs.

Best use cases

Legacy WordPress Site Preservation

Organizations with existing WordPress installations that depend on the classic editor and want to avoid forced migration to Gutenberg can migrate to ClassicPress to maintain workflow continuity while reducing bloat.

Performance-Sensitive Deployments

Content-heavy sites or hosting environments with resource constraints benefit from ClassicPress's ~50% smaller footprint, reducing server load and memory consumption compared to modern WordPress.

Custom Plugin & Theme Development

Agencies and developers building bespoke CMS solutions prefer ClassicPress's stable, minimal core for faster custom development and lower risk of breaking changes from major WordPress architectural shifts.

Implementation considerations

Verify plugin and theme compatibility before migration; not all WordPress plugins are guaranteed to work with ClassicPress's frozen feature set.
Plan for long-term maintenance: community-led updates are slower than WordPress; security patches and PHP version compatibility require monitoring.
Assess existing WordPress skill transfer: developers familiar with WordPress will adapt quickly, but Gutenberg-focused teams may experience friction.
Establish a security audit process since ClassicPress may lag WordPress vulnerability disclosures; review the fork's security update cadence.

When to avoid it — and what to weigh

Block Editor Dependency — If your workflow, plugins, or team skills depend on Gutenberg or Full Site Editing, ClassicPress removes these entirely and will require significant rework.
Enterprise Support Requirements — ClassicPress is community-led with no commercial support contracts. If your SLA mandates vendor support, security patches SLAs, or enterprise indemnification, this is unsuitable.
Latest WordPress Features — ClassicPress is forked from WordPress 6.2 (2023 era) and diverges from WordPress mainline development. New WordPress features and security patterns post-fork will require manual evaluation.
High-Volume Plugin Ecosystem Dependency — Many modern WordPress plugins target Gutenberg and newer APIs. ClassicPress users may encounter incompatibilities or plugin abandonment if developers cease supporting the fork.

License & commercial use

ClassicPress is licensed under GPL-2.0 (GNU General Public License v2.0). This is a copyleft license requiring derived works and distributions to also be GPL-2.0 compatible.

GPL-2.0 permits commercial use, deployment, and service offerings without explicit permission, provided modifications are made available under GPL-2.0. However, proprietary plugins or themes must be GPL-2.0 compatible. Commercial support, hosting, and implementation services can be offered; review GPL-2.0 terms carefully if bundling ClassicPress with proprietary software. Requires legal review for your specific commercial model.

DEV.co evaluation signals

Editorial assessment — not user reviews. Directional, with an explicit confidence level.

Signal	Assessment
Maintenance	Active
Documentation	Adequate
License clarity	Clear
Deployment complexity	Low
DEV.co fit	Good
Assessment confidence	High

Security considerations

ClassicPress inherits WordPress 6.2 security baseline and applies community patches. However: (1) security disclosure timelines are unknown and may lag WordPress advisories; (2) audit history is not published; (3) smaller team increases patch velocity risk; (4) third-party plugin security depends on maintainers' vigilance. Recommend security audit before production deployment and ongoing monitoring of ClassicPress security updates and WordPress-derived CVEs.

Alternatives to consider

WordPress with Classic Editor Plugin

If avoiding Gutenberg is the primary concern, installing the Classic Editor plugin on WordPress 6.2+ preserves block editor removal without forking, keeping access to latest WordPress features and plugin support.

Ghost

Purpose-built, lightweight Node.js CMS targeting creators with clean, modern UI and built-in membership/subscription features; smaller footprint and lower maintenance than ClassicPress for publishing-first workflows.

Statamic

Modern, Laravel-based open-source CMS with headless capabilities, flat-file or database storage, and contemporary developer experience; better for custom content models and decoupled architectures than ClassicPress.

Software development agency

Build on ClassicPress with DEV.co software developers

Our experts can assess ClassicPress compatibility with your existing WordPress infrastructure, conduct security reviews, and plan migration or deployment strategies. Contact us for a technical consultation.

Talk to DEV.co

Related open-source tools

Surfaced by semantic similarity across the DEV.co open-source index.

forkcms typo3 reactpress

Related on DEV.co

Explore the category and the services that help you build with it.

Open-Source CMS Web App Development Custom Software E-commerce Talk to DEV.co

ClassicPress FAQ

Is ClassicPress still receiving security updates?

ClassicPress is actively maintained with automated testing and recent commits. However, security patch timelines and disclosure procedures are not explicitly stated. Contact the maintainers or review security advisories for current SLA. Assume patches may lag WordPress core by days to weeks.

Can I use WordPress plugins and themes with ClassicPress?

ClassicPress maintains WordPress API compatibility (forked from 6.2), so many plugins and themes work. However, Gutenberg-dependent plugins will not work; test compatibility before migration. Fewer maintained plugins target ClassicPress specifically.

What hosting providers support ClassicPress?

Any PHP 7.4+ host with MySQL/MariaDB and standard LAMP support can run ClassicPress. No specialized hosting is required. Confirm with your host that they support WordPress 6.2-era codebase compatibility.

Is there commercial support available?

ClassicPress is community-led; no official commercial support is listed. Community forums, GitHub issues, and third-party consultants may offer support. Evaluate sponsorship or professional services through the community network.

Software developers & web developers for hire

Adopting ClassicPress is usually one piece of a larger software development effort. As a software development agency, DEV.co provides software development services and web development expertise — pairing senior software developers and web developers with your team to design, build, and operate open-source cms software in production.

Ready to Evaluate ClassicPress for Your Team?

Talk to DEV.co Schedule a Consultation