Thanks for sharing @avyas. Your blog looks great! I’m happy to see ClassicPress fits your needs and was able to deliver a better content management experience. I saw you like to use markdown, if you haven’t seen yet we do have two markdown plugins Markdown and there’s also peendev-markdown, which uses EasyMDE Markdown editor.
Many thanks for the feedback and the information on the Markdown plugins- they are absolutely fantastic!
Makes my writing workflow much more streamlined.
Best regards,
2 Likes
Hi everyone!
ClassicPress had been in my backpocket as an option for awhile now-- out of all the blogging alternatives I’ve tried, I wanted to stay in the WP/CP ecosystem. I thought to myself, “if I ever get really fed up with WordPress’ practices (read: enshittification) , I have something to fall back on.”
I hated the block system when it was first implemented. I got used to it, eventually, but I never liked it. I tolerated it. And I really didn’t like how simple customization was now behind a paywall, because Blocks.
After the leak of Attomatic planning to sell content to train AI models, I finally stopped waffling and made the plunge. Before I knew it, I had ClassicPress installed, patches updated, my site migrated, and I’m getting pretty cozy.
I’m enjoying my experience, so far! Not only it’s a CMS I’m familiar with, but it’s one I’ve missed.
EDIT: Pardon the dust; it’s currently up but I’m still shuffling around: Raintree Ruckus
9 Likes
Now that V2 is finally here I’ve moved my live site to it - I’d been running CP on my development machine for a while making sure my homebrewed plugin worked properly with it - but finally took the plunge. I might be imagining things but it seems to be faster than WP 6.4
6 Likes
I have around 10 sites running 1.7 or higher. Two of them are client commercial sites and the page load time they are impressed with the most. I have 6 to promote CP themes: http://classicpress-themes.com is one but not my favorite. I like the one for https://melody.tradesnet.us/ uses Melody theme for CP.
3 Likes
2 posts were split to a new topic: Testing ClassicPress
CP is notably faster than WP in every way. WP tends to load block related CSS into every page and greatly affect performance. CP on the other hand is great, no bloat.
My production site doesn’t use CP right now (Sorry!), partly due to my own theme doesn’t support classic widgets right now, and would require block CSSes for a basic styling. But I will move all my sites to CP eventually 
I was surprised that CP supports SQLite Intergration BTW.
3 Likes
wordpress developer do not want listen community: true!
but there are options, like Disable Gutemberg…
1 Like
Are you still interested in helping with translations? We have the process all set up now, but we don’t have anyone to translate into French.
1 Like
5 years and counting… yeahh… 
https://www.marialenasarris.com/migrating-my-website-to-classic-press-cms/
2 Likes
I’ve been using ClassicPress for five years. I was too angry about the introduction of Gutenberg, and I was hoping that WordPress would get back on its feet. And yet not only did he not do it, but he actually extended that system to everything: widgets, theme development, and in some ways even plugins.
For me there was no other choice. I remember wondering if there was a fork of WordPress somewhere. I said to myself: damn, they fork everything today, and there is no one who has ever thought of forking WordPress, as arduous a task as it was.
But in reality, I wasn’t thinking of cms without Gutenberg, I was thinking of a different CMS. So much so that before coming across ClassicPress, I also took a look at WordPress’ little brother, that is, the other fork of Cafeblog/B2, B2Evolution, but nothing that really excited me. Furthermore, although it was a fork of Cafeblog, it had very little to do with WordPress. Then I even thought about Drupal… But I ran away. 
Then, browsing the web, I found ClassicPress, and I didn’t believe what I saw. Since then, I no longer use WP for my live sites, and I have also installed it on the sites of acquaintances and friends.
I hope the project grows more and more. And I believe that if many bloggers and site administrators who struggle with blocks today knew ClassicPress they would not hesitate to ferry their sites with CP. However, it is a real shame that hosting providers do not include it among the available installations. Mine doesn’t have it.
6 Likes
Not exactly sure what email marketing you are talking about, but the days of sending email from your blog are over because email providers have a cartel designed to block outsiders. (I don’t really blame them, spam is horrible.)
In any case, I’d assume most email marketing apps use a 3rd party service to actually send the email, which means they should be compatible with ClassicPress too. Last I checked, WordPress itself has no code related to email, so you’re not missing anything there.
FWIW, it is possible to setup an email server on your blog server, but last time I tried this it took me about three days, very complicated, not very fun
1 Like
True. You don’t want to use your domain or your personal email for email marketing. Find a service you like and let them have the headaches of keeping it whitelisted everywhere.
I chose ClassicPress because I appreciate its focus on simplicity and security. It’s a great option for those who value a clean, lightweight platform without all the bloat of WordPress. Plus, the ClassicPress community is smaller and more tight-knit, which I find to be a positive.
5 Likes
Fully agree! Same here, and we had a big project at the time, which caused us some concern to stay on the WP platform. But CP wasn’t launched yet.
1 Like
Let me just give the correct info here.
ClassicPress first ever rc release was announced here on this forum during February 2019 and the corresponding release of v1 stable (codename Aurora) happened on the 3rd March 2019. CP alpha version was launched in late 2018, and reached the production level in March 2019.
Your profile on the forum dates back to Dec 2019, so this means that you joined CP when v1 was already a thing.
Clearly you can say the ecosystem at the time was small and community was still trying to gain traction and build awareness. But please be precise. Saying it wasn’t launched means entirely another thing.
At the time you might have not felt ready to use it for the project you mention, this does not mean it wasn’t production-ready and stable. CP is so stable even the nightly builds are stable enough for production.
4 Likes
Elisabeth, You misread my post and interpreted incorrectly.
What I said was “But CP wasn’t launched yet.” - which it wasn’t. If it was, we certainly would have considered it.
Gutenberg was being introduced very early as a dev plugin, back in the Spring and Summer of 2017. We had a big union project rolling out at the time. Of course ClassicPress wasn’t rolled out yet (Aug 2018 I recall). We launched our project in Oct. 2017 a year before CP. SO when I found CP in the works, I was pretty happy about that.
I was replying to @iljester comment about Gutenberg, which made me feel the exact same way. That was my point.
1 Like
Sorry, i really misunderstood then. I thought your comment referred to the time you discovered CP. not before it
1 Like
NP Elisabetta. I didn’t really provide any context, so I can see it being interpreted any which way. It’s a good point though, to provide context to things - so I will keep that in mind.
3 Likes