For this class, I’m not using an LMS at all.
For most of my other classes, I use my own concept, Webby Books, which are built on CP.
2 Likes
About a year or maybe two ago I surveyed the members of a small business mastermind community I was running.
Many of those taking the survey were serious writers who either owned their own sites or made a living contributing on mostly WordPress sites.
At that time, only three out of twenty-something used Gutenberg at all. And none of them used it for their blogs - only for landing pages or their home page.
The reason I switched to CP was concern that WP would try to eliminate the ability to use the ClassicPress Editor. I knew I was NEVER going to want to use Gutenberg.
When Gutenberg launched, reviews on WP were 50% ratings of 1. People either hated it or loved it with over half hating it. I doubt that has changed much.
I edit content for a client who has Gutenberg running. Thankfully, the content I’m editing is old enough that it is all in one Classic Block and not a bunch of other blocks that make content difficult to edit.
Blocks make zero sense for a long-form writer. We edit, add, move text around and then add images, videos, etc. Using blocks is painful.
And Gutenberg is still flaky. The writers who took my survey hated having to use it on some sites. They complained of how much longer it took and how quirky it was.
I run into odd issues just editing a Classic Block. I pray that all of the content is either using Classic Blocks or what I edit will be old enough to have been converted into one.
They don’t actually use Gutenberg as they are running the Breakdance page builder.
Actually WP has pruned a lot of 1-star reviews, so the numbers were originally even higher.
cu, w0lf.
1 Like
This use of corporate power to change and influence perception is what makes official WP even worse.
WP since Gutenberg was forcefully introduced has lost it’s way IMHO.
Since Gutenberg there was nearly 0 actual useful featured developed for actual web devs who needed a good CMS to run their backends and focused on page building which they made a worse job at that.
The core of WP should be focused on the CMS side, that’s why I’m now starting use CP on all my sites.
3 Likes
There is not enough ( Confident Talk ) about classic press for people to consider moving
Lets be honests and im going to share my first experience with classicpress this year, because first time i tried was last year and i had a computer with windows and i used xampp xDDD
i use linux, and my first question was, how am i going to install and run it
Checked documentation, server side is pretty okay ( as the usual stuff, ssh or ftp, upload things, create database, run the url, install it )
Docker option, docker image is there, we can run the docker image, but the setup requirement is very manual, ofc, classicpress does not have enough man power or probably prioritize something easier for a docker ready to run like wp-env as example
mention of local by flywheel, it is there, but not the steps, yeah, we can figure it out, thats okay, just install a wp site with Local, delete everything inside of public folder but not the wp-config
it will ask for a database update, ready to go
or, people can still go with the normal xampp, lampp, etc
What i mean is, i dont know how long people here at classicpress left wordpress behind, and if people still follow wp or not
The truth is that, things are changing, people now a days if they have to change a config file they are already sweating ( % of people )
WP, right now have 3 types of users regarding the usage of tools
1 - classic ( classic themes )
2 - block themes ( 50/50 ) the ones that uses and loves it, the ones that uses and complains about it
3 - the page builder world
I would say, with the Block theme and Gutenberg, most people are actually moving to page builders once they are done exploring the FSE and understand that it actually does not satisfy the minimum requirements of modern development in 2024/25
Because it does not
However, does classic themes satisfies that requirements as well? If, the user is a developer, then yes
PHP as server side, html, css, JS, ( a normal stack )
But, we all know, the biggest % of users of all the wordpress websites, are non tech users
A simple blog with some theme installed, or some theme forest A, B, C installed
However, if classicpress doesnt make it easy ( easy for everyone including the non tech ) to try it, then people will come, visit, download, try, and at first trouble, they exit
I actually came here this year because someone reported and asked support on Automatic.CSS for a compatibility problem, so i came check it out, and the plugin fixer for bricks was really just because i did see a user saying that he did put the code on the theme codebase, which will be disposable off in the next update
but from those of us who tried to easily get an instance of classicpress up and running, we found errors at first try
and is that feeling that i want to show here on this reply
the feeling is mostly:
classicpress? okay, i know is a fork, lets try it
how to put up and running in the modern day? let me try a old cpanel hosting i have somewhere
install a theme ( that link expired error ) " off to a good start "
should i invest more time trying or just give up?
and that is the reality
Now, as an honest opinion, i think all here are doing great, classicpress works, is a working fork, is a standing still fork, and thats important
WP is on a dark cloud right now, it could be beneficial to classicpress, and i dont mean on a way of ( having milions of users ), but it could be an opportunity to have some more thousands, at least to have a little bigger community
Nice job all 
1 Like
I don’t disagree, but essentially that’s just another way of saying that we need more people involved! 
Every project needs a critical mass, and we aren’t quite there yet.
1 Like
@Hakira-Shymuy thanks for the content suggestions. I write a series about CP. I will try to incorporate some posts answering your questions.
Gimme time however because I have my hands slightly full and I am only one.
2 Likes
@Hakira-Shymuy I do not agree with your classic themes statement. Yes, they do cater to developers, but we have built countless websites and thrived before the block editor has been introduced. I, honestly, look back to those times with nostalgia.
I agree that, in the agency I’m working, the block editor is very useful for our marketing team and our clients.
But the overhead, the slowness of WordPress right now, the inability to build blocks because… ReactJS, and the future (rather scary) plans of bringing the Site Editor as the main content editor, is pushing developers away. And without developers, there is no WordPress. And then WordPress turns to Wix.
ClassicPress classic themes can be enhanced with custom fields, metaboxes, theme options and more. Because in my experience, non-tech-savvy users won’t mess with the design if the theme is properly built.
I have a flagship theme I use for all my projects. It’s mostly a shell, with options for headers, footers, template parts, dimensions, colours, and fonts. Everything else is built by the page builder (block editor, TinyMCE, FX Builder, etc.)
With a large enough theme selection, I think ClassicPress will thrive.
6 Likes
thanks @Ciprian for saying this!
3 Likes
Hm, not sure i understand what you do not agree regarding classic themes, and that might be my fault here.
I think i did not gave enough context on why said
Blockquote
However, does classic themes satisfies that requirements as well?
So let me give more context here, that why you dont interpret me in the wrong, and perhaps i will understand more where you disagree
When i asked if classic themes satisfies that requirements as well, i was referring to:
the 3 types of WP World users ( talking about Majority of % of WP users, and thats more than 50% )
1 - classic themes used to be a bunch of files and functions and templates, integration with ACF, and ACF on the backend to accommodate custom fields to create a more dynamic and bespoke website
2 - page builders generation, those themes, soon realized that page builders are actually an easier way to cater for example, DIY websites users, Web Designers with no coding knowledge, Marketeers, etc
2.1 - in those, we can talk about, beaver builder, wpcomposer if we go more back in time, divi, elementor, etc, even more modern ones like Bricks Builder
3 - Blocks/FSE Generation ( no comments here )
So, when i asked the question, i was actually talking and referring about the point 1.
That themes, used to rely on ACF, Pods, as the data type inputs for a more bespoke content, and thats not viable in terms of modern websites, modern development and user experience on the Today generation
People started to understand the need to customize and tweak per breakpoint, a more bespoke website, doing it themselves, because page builders did bring that to the table
So very easily a person on a small town, could actually do a better looking website, or a web designer could easily create a portfolio
That is the page builder generation, and they still use classic themes
But if we step back from this generation, then we are left with users that have 2 options
1 - or they have coding background and they craft their own theme
2 - or they get themes from themeforest and they tweak it with whatever options the theme offers
Thats the context of my question
I think that, a good approach to try cater some of those users ( they are still milions ) would actually ( try ) to have some talks with page builder developers and classic theme developers, to try to have a better compatibility with ClassicPress, i believe its easier for them to do that step than being ClassicPress trying to have tons of files with shims
Regarding blocks, i sort of understand them, the idea ( would not be bad ), it was very poorly executed IMO, and to me, is a tool Only to write blog posts, is not ready for anything else other than that
2 Likes
Hi, I’m quite new here. I am a web developer (probably one of many) who got turned off by the complexity of modern WP (the full site editor is a nightmare as well as the block editor, I never got used to it, that’s why I avoid it, but maybe I’m too old?), so having the “simple” old WP back in ClassicPress is why I’m here (and btw I’m also fond of Grav CMS).
Simplicity is the way. Today’s world is getting overly complicated.
I don’t have much experience/feedback what general users and customers say to block themes and the full site editor, but I can imagine that many of them would rather spend an extra hour comparing different classic themes to find the right one, instead of learning how all the new “features” of modern WP work.
7 Likes
Welcome, @amarok!
2 Likes
Always nice to see another Grav fan
2 Likes
In another discussion we covered which page builders already work with ClassicPress:
"We do have Beaver Builder publicly supporting CP.
FX Builder was developed for CP by forking a plugin for WP and I have it on some of my sites because it’s just GREAT.
Thing to note BB and FX are not compatible with one another but that is not a problem since one of the two is usually enough to develop a site."
fwolf Founding Committee Member
"Re: Page Builders working with CP
Technically, Visual Composer (or whatever its called nowadays) should also work with CP, as it basically is just a nice UI for a shortcode orgy.
There also is some kind of Bootstrap-specific page editor that looked promising a few years ago, but I sadly cant seem to find it at the moment. Still, got its sources saved here somewhere (also, it was on github … I think), so it should be still good.
cu, w0lf."
2 Likes
The older I am, the simpler solutions I seek, life is already hard enough 
So Grav is one of several good choices if I need a CMS, it’s so easy to get started with and build something. Sometimes I prefer pure html/css/js/php without anything else to build a simple website or web app, I’m kind of old-school. Modern frameworks like Laravel are a nightmare, I gave up learning it, but I create simple sites anyway, Laravel is maybe more suitable for huge sites.
3 Likes