ClassicPress (@[email protected])

Build your website or a blog today using a lightweight, stable, instantly familiar fork of #WordPress without the block editor & FSE. * Better performance * Better privacy * Community-funded * 501(c)3 non-profit classicpress.net #CMS #FOSS #OpenSource #PHP #WebDev

@mikemcalister @toniievych ClassicPress isn't trying to compete with WordPress. It offers a simple, clean alternative for those who need it. Some people want the comfort of an RV to go on a road trip, but others prefer to do it in their regular car. Both get the job done, but they meet different needs.

Rolling out an industry-changing update to complex software that powers nearly a billion websites was never going to be fast or easy. Sure, lots of little things are missing, but still, you can build a beautiful, fast website with *native* WordPress today. The implications are staggering.

🎨 Thoughts on the Upcoming #WordPress Admin Redesign I recognize there are going to be inevitable hurdles to cross for this update, I also think this is a time in which lessons learned over the past few years can be applied. tommcfarlin.com/the-upcoming-w…

@tommcfarlin I don't think that Matias has learned a lesson with Gutenberg. We'll see another Classic Admin plugin with millions of installs and more support for @GetClassicPress

@josecontic @GuardianesWP @josuezarcoOU Ese es el problema José. Que no hay retorno, pero sigue teniendo mercado. Hasta el punto de existir el fork sin GB aka @GetClassicPress. Y luego hacen cosas como está que comentabas de los hosting, y que te recuerdan de quién es la pelota con la que todos estamos jugando...

@tehseowner @victorjonsson @seonobull Thanks. Will wait for your DM.

@GetClassicPress @victorjonsson @seonobull I will send the functions I’m using to remove the JS/CSS from backend, and also my JS. Admittedly I’m not a JS coder (mainly proficient at PHP), so it’s pretty basic stuff. But I’m sure you can improve on it and/or convert to Vanilla JS (depending on performance). Will DM soon.

When I'm saying we are very reluctant, I mean it. This is not a random site, it's a real money maker and on 4.8.23 version. Of course if you're a noob with a new site go ahead and update.

@tehseowner @victorjonsson @seonobull Thanks. I'll have the team review this. In v2.0, we removed a lot of JS packages, that could affect your results. But it shouldn't be slower than WP. If you would like to share your JS, we can take a look and consider it for inclusion. We're trying to reduce JS usage 😀

@GetClassicPress @victorjonsson @seonobull Point is, I'm surprised my plugin had no impact at all... there's something deeper than surface-level things causing the delay. I've tried other configurations, disabling plugins, enabling them. Btw, the screen above with my plugin is both ClassicPress (both 1ms).

@tehseowner @victorjonsson @seonobull Thanks. Are you using classic editor or is it the default block editor? Want to make sure we test the right thing.

@GetClassicPress @victorjonsson @seonobull I have many hundreds of Wordpress sites and development them offline. This is on the same localhost installation, PHP 7.4, Apache 2.4.53. These are the speeds on the backend when clicking "Posts". The frontend is almost 2x faster TTFB, which is incredibly impressive.

@tehseowner @victorjonsson @seonobull How are you measuring backend performance?

@victorjonsson @GetClassicPress @seonobull The backend (v2) is slow, even with my custom optimization plugin that removes all bloat. BUT, the frontend is legitimately 2x faster TTFB. I did not expect that sort of change, but it makes sense considering all the block php files aren’t loading.

@victorjonsson @tehseowner @seonobull Thank you, we appreciate your kind words 🙏

@GetClassicPress @tehseowner @seonobull Yeah, it's been a while, so I didn't know about the 2.0 🙂 Great job, love the work you're doing!

@seonobull Heck, i'd even consider using classicpress for a custom site. Rock solid, lightning fast

@victorjonsson @tehseowner @seonobull The project is doing fine 😉 Our upcoming v2.0 is based on WP v6.2. Lots of accessibility improvements. More plugins & themes will be compatible. Our v1.x is compatible w/ WP v4.9 plus some functions from v5+ but plugin compatibility can be an issue, so it's important to test.

@tehseowner @seonobull I'd definately consider it, if I was going to make some sort of tool or platform for my use only. They port security- and performance updates. But it's been a while, so I'm not 100% what the status is of the project. But at the core it's stable and solid

@schutzsmith Admittedly I’m still #ClassicPress but it’s because for my clients I use @wp_acf and completely hide the content editor, etc. to limit them to simply filling in the fields I set up for them. Especially in the corp/gov info site space, they’re simply entering in new content.

@TheCre8tiveDiva you can try @GetClassicPress (a fork of WP 4.9 nearing its v2 release). it has the customization of login page with your logo directly from the admin page (it is not yet possible to link your logo, but you can submit a feature request for that).

@codeshah @bretwp Not a lot of money, but we have dedicated volunteers working on ClassicPress 😉

@bretwp After all the drama, I also wished some robinhood would come and fork the entire project, pour a lot of money, hire all the volunteers full time and not repeat the history 😂

WordPress folk Do you really think they should fork WordPress into Classic and Gutenberg versions? I personally don't I think if they did, Classic would still run the internet and Gutenberg would gain 'some' traction but ultimately be defeated by the 'other' platforms

@bretwp Isn't this what you're referring to? Not sure how much traction has it received. classicpress.net

@ajaydsouza @CSDevAr @bretwp That's right. Our v1.x is based on WP v4.9. Our upcoming v2.0 is based on WP v6.2.

@CSDevAr @bretwp I think it came about around five years back when WP 5.0 launched.

@bretwp They did in version 4 though @GetClassicPress 👍👍

@ellenbauer @felixarntz blocks are blocking me. I went for @GetClassicPress as soon as blocks were out in late 2018 - five years down the road without looking back.

#ClassicPress 1.7.0 now available (major update). installatron.com/classicpress installatron.com/updatefeed/cla… @GetClassicPress #installatron

Updated : ClassicPress -> 1.7.0 @GetClassicPress

Hi @ManageWP Do you support @GetClassicPress? And if you do, will you support it going forward? You may be aware that long-form content bloggers do not use Gutenberg. So if the plugin goes away, they will need to use something besides #WP.